12111 - [RFE] Browser modes, eg normal, view source, view DOM, etc

Status: RESOLVED WONTFIX

(SeaMonkey :: General, enhancement, P3)

Description

[Matthew Tuck [:CodeMachine]]

This is a proposal to view the page source in the same window as the main
browser window, with the web page content being replaced.  There would be a
toggled menu item and toolbar button to change between the two.

I suppose this might eventually be a mode of "transformation services", since
page source is just a transformation of HTML into HTML that renders the source
rather than the page.  Hence eventually you might have other "modes" viewed
inline, possibly chosen by tabs on the toolbar.

I propose this inline behaviour is what would be most commonly desired.  If you
needed to compare the two side by side you could open another window.

Comment 1

[Matthew Tuck [:CodeMachine]]

I split this off bug #11519.  Setting M14 just like you like them Don.  =)

Comment 2

[Matthew Tuck [:CodeMachine]]

"and toolbar button" should read "and possibly toolbar button".

Comment 3

[Matthew Tuck [:CodeMachine]]

Bug #12111 would be an extension of this, including a third mode for the new DOM
viewer, and could use a UI similar to bug #11140.

Comment 4

[Matthew Tuck [:CodeMachine]]

Another extension is bug #11520, ability to view stylesheet source.  I've
changed the description to reflect the more general nature.

Comment 5

[don]

Move to M20.

Comment 6

[Paul MacQuiddy]

updating qa contact

Comment 7

[don]

Move to "Future" milestone.

Comment 8

[sairuh (rarely reading bugmail)]

pardon the spam: moving view source bugs into xp apps: gui component.

Comment 9

[Jesse Ruderman]

*** Bug 58868 has been marked as a duplicate of this bug. ***

Comment 10

[Viswanath Ramachandran]

Since Don has left, Vishy is taking his bugs in bulk, pending reassignment.
thanks,
	Vishy

Comment 11

[Blake Ross]

-> UI:DF

Comment 12

[Matthew T (active 1999-2002)]

Modality is ok, as long as it increases the user's productivity, and as long as 
three things are made very clear in the UI:
(1) what mode the user is in now
(2) why the mode exists
(3) how the user can switch to a different mode.

I don't think there is a UI design possible for which `browser modes' can make 
these three things clear, without spoiling the browser interface for the 
majority of users who don't care about source code or the DOM. If you show the 
source or DOM in a separate window, it's fairly obvious that you can get out of 
that mode by closing the window (since the original browser window is still 
there). But if they were shown in a browser window (as this bug is proposing), 
I don't think you could show the modality clearly enough. And as for 
productivity, any increase caused by implementing this suggestion would be 
marginal at best.

Convince me I'm wrong, otherwise this is a wontfix.

*   If a user selected the menu item by mistake (e.g. if they moused up by
    mistake while dragging to an item lower down in the `View' menu), how would
    they know how to return to the original mode?

*   Given that most Web users couldn't care less about page source, how could a
    button for it on the toolbar, or a row of tabs for `browser modes', be
    justified? And if the button was only present if the user was in a mode
    other than `Normal', then (a) where would the button go, and (b) how would
    users become familiar enough with it to know how to use it if they needed
    to?

Comment 13

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

It sounds to me that a "Web Developer" menu and/or toolbar might be very 
appropriate for this. Then you would have a place to put the "View 
Source"/"View DOM"/"View Stylesheets"/etc. items. Then you would have a pref 
for showing or hiding the "Web Developer" menu and/or toolbar. By default, the 
pref would be "off"; web developers should know how to change preferences at 
least as well as non-developers.

Comment 14

[Jonadab the Unsightly One (Nathan Eady)]

I agree with comment #13, a web developer toolbar, not visible
by default but able to be turned on under View->Show/Hide makes
good sense to me.  I am sure there are other things that could 
be placed on it besides just what this bug is requesting.  
(Think in terms of validator.w3.org and similar resources,
though that is clearly beyond the scope of this RFE.)

Web developers are not the typical users, but they are an
important niche because they tend to drive what browser(s)
other users use.  (This may be unfortunate, but it is true.)

Comment 15

[Matthew T (active 1999-2002)]

Wontfix for the reasons given in comment 12.

Comment 16

[YHONNY HERNANDEZ]

Attachment: (deleted attachment)