Closed Bug 269762 Opened 20 years ago Closed 19 years ago

"Show this frame only" error!

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED EXPIRED

People

(Reporter: webmaster, Assigned: bugzilla)

References

()

Details

(Whiteboard: [sg:nse])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When you are on a double-frame page (ex. left menu, right contents) and you open
a link from the menu, that link targets the right menu, and that's ok. But if
you right-click the contents page and select "This frame" >> "Show only this
frame", and then you make an history back, ALL the links on the menu frame, will
be displayed as target="_blank" links instead that inside the content frame.

Reproducible: Always
Steps to Reproduce:
1. Open for example the phpmyadmin database manager.
2. Select a link from the left column.
3. Right click on the contents page and then This frame >> Show this frame only.
4. Click back on the Navigation toolbar.
5. Click any of the left frame's links.
Actual Results:  
All links open in a new page (target="_blank" behavoir).

Expected Results:  
The links should keep opening in the right frame.

I'm using Firefox 1.0 official release (not beta or preview), without any plugin
or themes. Just installed and tried. I think that this can be a security bug
under some conditions.
This is not an accessibility bug. Please read the component descriptions (under
the "Component" link) before filing a bug. Accessibility is for usability by
persons with disabilities. See http://www.mozilla.org/access for more info.
Assignee: aaronleventhal → firefox
Component: Accessibility → General
QA Contact: bugzilla → firefox.general
this is not a security bug either.
Group: security
Whiteboard: [sg:nse]
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/
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
You need to log in before you can comment on or make changes to this bug.