Closed
Bug 247070
Opened 20 years ago
Closed 20 years ago
FireFox 0.9 doesn't recognize the use of <base target> in frames
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 248753
People
(Reporter: guillaume, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.9
Two frames on a webpage (which I can't provide as it is private) : one on the
left, on the right. The left frame hase a base target for every link in it and
this base target points to the right frame. But when I click on a link nothing
happens as if FireFox 0.9 couldn't understand it.
No problem whatsoever with FireFox 0.8 and I did a clean uninstall / reinstall.
Reproducible: Always
Steps to Reproduce:
1. get a framed site with base target
2. click on a link that use the base target
3. nothing happens
Actual Results:
Nothing
Expected Results:
Open the link in the "destination" frame
Comment 1•20 years ago
|
||
worksforme linux firefox 0.9, with base target frame for links specified in
head, as in <base target="frame2">. Provide a testcase and reopen if you still
see this.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
(In reply to comment #1)
> worksforme linux firefox 0.9, with base target frame for links specified in
> head, as in <base target="frame2">. Provide a testcase and reopen if you still
> see this.
Don't understand a single word : I'm not running Linux but Windows. Here is a
copy of the source of our site :
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
<TITLE>Assitant</TITLE>
<BASE target="bigpage">
</HEAD>
With FireFox 0.8 or FireFox 0.9 RC there was not problem. With FireFox 0.9, the
<base target> isn't working and all the links in the frame do nothing.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 3•20 years ago
|
||
Using that HEAD snippet works fine for me as well. As a random guess, this might
have something to do with bug 246448, if your frames/frameset are from different
origins, or something to that effect.
Comment 4•20 years ago
|
||
I and many people cannot see bug 246448 ('You are not authorized to access bug
#246448.')
Does you say about below?
3rd section of Known Issues
http://www.mozilla.org/products/firefox/releases/index.html
Comment 5•20 years ago
|
||
(In reply to comment #2 & comment #4)
Completely same situation as Comment #2 was reported to Bugzilla Japan and it
was bypassed by setting "docshell.frameloadcheck.disabled" to true.
(In reply to comment #5)
> (In reply to comment #2 & comment #4)
>
> Completely same situation as Comment #2 was reported to Bugzilla Japan and it
> was bypassed by setting "docshell.frameloadcheck.disabled" to true.
>
>
Where do I set this "docshell" stuff ? Thanks.
Comment 7•20 years ago
|
||
(In reply to comment #6)
"How to" is described in Known Issuus section of Release Notes which is kindly
linked by comment #4.
Read Release Notes of Firefox 0.9 or 0.9.1.
Comment 8•20 years ago
|
||
This was fixes in bug 248753.
*** This bug has been marked as a duplicate of 248753 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•