Closed
Bug 185793
Opened 22 years ago
Closed 19 years ago
Requesting right-click -> "This Frame" -> "Go back one page" menu option
Categories
(Core :: DOM: Navigation, enhancement)
Core
DOM: Navigation
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: vroemisse, Assigned: radha)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
I'd like to see a menu option "Go back one page" in the "This Frame" submenu
when right-clicking in a (i)frame. This, of course, should be accompanied by a
"Go forward one page" option.
Severity: request for new feature in R3 :)
Reproducible: Always
Steps to Reproduce:
Comment 1•22 years ago
|
||
Maybe I misunderstood you, but why dont you simply right-click and choose Back
or forward in the menu?
Reporter | ||
Comment 2•22 years ago
|
||
Because that might work on another frame than the one I want to go back. It
often does.
Comment 3•22 years ago
|
||
->History:session
Assignee: asa → radha
Component: Browser-General → History: Session
QA Contact: asa → claudius
Comment 4•21 years ago
|
||
*** Bug 211820 has been marked as a duplicate of this bug. ***
Comment 5•21 years ago
|
||
Hi- I had entered this as a new bug & the developers suggested I move th
testcase here. They pointed out the back/fwd buttons were doing what they
wanted them to- reversing the actions taken (i.e. going back in one frame, then
the other if that was the way I navigated there). I still think a "Back in
frame" is a good idea on the "this frame" menu.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a)
Gecko/20030703
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a)
Gecko/20030703
If I try to navigate just one frame in a 2-frame (split screen) page, then the
back/forward buttons seem to randomly apply to one frame, then the other.
Reproducible: Always
Steps to Reproduce:
FOr an example, go to http://imaging-resource.com/IMCOMP/CDISPLAY.HTM
select a camera in each frame, then select images in both frames until you end
up with a high-res photo in each. I did this alternating between the frames
(that is, click in LH frame, click in RH frame). Then try to navigate back in
just one of the frames back to the originally displayed page. It isn't possible.
For example, click in the LH frame blank area between the title, then press the
browser "Back" button. CLick in the LH frame again and press the Back button.
The RH frame goes back not the LH frame.
Actual Results:
The wrong frame goes back, and the navigation requests seem to randomly go to
one frame then the other.
Expected Results:
Performed the navigation request on the frame that was under the cursor at the
time, or that had the "focus" (i.e. the user had clicked on it).
Alternatively, offer a specific frame back/forward navigation option that is
sensitive to the "focussed" frame.
Either:
1) the browser needs to be aware of which frame the user wants the action to be
performed on (a "focus" on the frame, albeit invisible), or
2) back/forward menu selections that are in the RH button menu popup should
apply to the frame that is currently under the cursor, or
3) the "this frame" submenu available from the RH button menu popup should have
a "back/forward in this frame" menu item available, that applies to the frame
currently under the cursor
Thanks!
Indulis
Comment 6•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 7•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•