quicker access to frame source (and info)

NEW
Unassigned

Status

--
enhancement
17 years ago
9 years ago

People

(Reporter: Martin.T.Kutschker, Unassigned)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
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.
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.  :)
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

17 years ago
i vote for wontfixed
(Reporter)

Comment 3

17 years ago
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

17 years ago
how about bug 137901 ?
(Reporter)

Comment 5

17 years ago
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?
Summary: quicker acces to frame source (and info) → quicker access to frame source (and info)

Comment 6

17 years ago
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

17 years ago
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

16 years ago
uid is being phased out.
Assignee: mpt → blaker
Component: User Interface Design → XP Apps: GUI Features
QA Contact: zach → paw

Comment 9

15 years ago
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

15 years ago
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.
Assignee: firefox → guifeatures
Product: Core → Mozilla Application Suite

Comment 11

13 years ago
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.
Filter "spam" on "guifeatures-nobody-20080610".
Assignee: guifeatures → nobody
QA Contact: pawyskoczka → guifeatures

Updated

10 years ago
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.