138400 - quicker access to frame source (and info)

Status: NEW

(SeaMonkey :: UI Design, enhancement)

Description

[Martin Kutschker]

The frame source and info used to be in the context menu, but moved into a
submenu of the context menu (in 1.0rc1). While it is nice to have all the
actions for a frame cuddled together it is a pain for web developing. Almost
every time I want to see the frame's source and not the frameset's source.
Please consider some rearranging.

I guess you won't bring frame source/info back, so think about bringing them to
the view menu (AFAIK there is a bug for this). This would be consistent with
"save frame" in the file menu.

Or simply move "this frame" up (eg. right under "stop" or right above "Bookmark
this xxx"). This would give you an overall quicker acces to the frame stuff.
IMHO also non developers would benefit from this.

Another solution would be to make page source/info tabbed for the frameset and
all the contain frames. A variation would be a tree instead of tabs to reflect
the frames' relationship within the dom.

Offtopic: please make the frame submenu non-scrolling.

Comment 1

[Boris Zbarsky [:bzbarsky]]

ccing marlon, who designed the spec, and confirming (though I suspect this will
end up wontfixed...).

> Offtopic: please make the frame submenu non-scrolling.

That would be bug 135076.  :)

Comment 2

[lancer]

i vote for wontfixed

Comment 3

[Martin Kutschker]

Wontfix because the problem is not a real problem? Or because the proposed
solutions are not good enough?

My favorite is "moving submenu up" (quicker access to all frameinfo for
everybody, even "normal" users), though I do support adding frame source/info
into the view menu.

I guess that developers would love the combined page/frame info. Perhaps I'll
create an xpi for that. Though I guess it will end up as an item in the new "web
developers" submenu.

Comment 4

[John Levon]

how about bug 137901 ?

Comment 5

[Martin Kutschker]

The suggestions in bug #137901 will destroy the consistency introduced with the
new changes.

To make Mozilla's you'd have either add "frame source/info" to "view" or remove
"safe frame as" from file. Though "text zoom", "use style", "character coding"
are still missing tasks for frames. Is there a bug for this?

Comment 6

[viipale+bugzilla]

As a web developer I'm also annoyed that the view frame source is now located in
a submenu. Please move it back where it was or give it a hotkey or something.. 

Comment 7

[Carl Schrader]

I think this should be more context sensitive. If you right click on a frame, at
least the reload on the main menu should reload the frame. I can't count the
number of times I have clicked Reload and then remembered that I needed to go to
Frame first. This could cause dataloss on some web applications, so it should be
given high priority. I cleanup and such is good for the most part except for the
reload. Maybe have Reload Page and Reload Frame on the main context menu?

Comment 8

[timeless]

uid is being phased out.

Comment 9

[Richard Körber]

I'd really like to have Ctrl-U opening the current frame's source, instead of
the frameset's source (which is quite uninteresting in most of the cases).

Comment 10

[Blake Ross]

Reassigning obsolete bugs to their respective Seamonkey owners (i.e. nobody). 
If you want this fixed for Firefox, change the Product and Component accordingly
and reassign back to me.

Comment 11

[Jim Reijers]

So this bug is not going to be addressed? :-(
It's been a huge (and rare) source of irritation ever since I've used Firefox.

Why not allow for configurable context menus... or simply two predefined sets: "developer" and "surfer", for example.

Comment 12

[Serge Gautherie (:sgautherie)]

Filter "spam" on "guifeatures-nobody-20080610".