Closed
Bug 469507
Opened 16 years ago
Closed 13 years ago
Firefox 3 doesn't find named frame, sets up new window instead
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: L.Wood, Unassigned)
References
()
Details
Just noticed that a frameset I set up doesn't work correctly in Firefox 2/3 - though it still works in IE just fine, and worked fine in Netscape for years. Clicking a word should bring up the dictionary definition in the entry_frame frame. Instead, it spawns a new window/tab in Firefox, presumably because Firefox can't find the entry_frame frame title for some reason.
Comment 1•16 years ago
|
||
Firefox 2 doesn't show this problem, only 3.x builds after late Jan 2008.
This problem is caused by the fix in bug 408052 and could be a duplicate of bug 431835.
Disable "Navigate subframes across domains" in IE7 (default value)
Internet Options > Security > Custom Level
If this gives the same result as Firefox, please close this bug as duplicate of bug 431835.
Reporter | ||
Comment 3•16 years ago
|
||
fixing title
Summary: Firefox 2 and 3 don't find named frame, set up new window instead → Firefox 3 doesn't find named frame, sets up new window instead
Reporter | ||
Comment 4•16 years ago
|
||
Fixed the problem with
http://www.ee.surrey.ac.uk/Personal/L.Wood/jargon/ -
compare with
http://www.ee.surrey.ac.uk/Personal/L.Wood/jargon/index-old.html
which showed the problem.
I have no idea why this modification works.
Reporter | ||
Comment 5•16 years ago
|
||
Ah, the modification only works for the first letter bringing up the index to that page. Subsequent selected letters spawn a new page. Why does this now work for the first frame load, but not subsequent?
Comment 6•13 years ago
|
||
Works for me, Nightly 12.01a (2011-12-26) on Linux.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•