Closed
Bug 194251
Opened 23 years ago
Closed 22 years ago
URL Bar shows URL of loading FRAMEs, rather than remaining at the FRAMESET document
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 195078
People
(Reporter: christophe, Assigned: saari)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
|
240 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.3b) Gecko/20030130
Build Identifier: ftp://ftp.mozilla.org/pub/chimera/nightly/2002-12-20-04/Chimera.dmg.gz
I have made a little test case, see at the end. This little test case works
perfectly with galeon 1.2.7, with the lastest mozilla but not with galeon
1.3.1 (which is linked with the last mozilla that pass the test). It doesn't
work correctly with Chimera (nightly build from 20 December).
Basically the problem is that Chimera ignores the "<base target=" tag
in a html file in a frameset.
With the following 3 files, if you open index.html and click the link, the
link should be opened in the frame main but instead it is opened as an
independant file (as if the target was _top).
<-- index.html -->
<html>
<head>
<title>Simple frame/target test</title>
</head>
<frameset cols="100%" rows="100%" border="0" frameborder="0" framespacing="0">
<frame src="test1.html" name="main">
</frameset>
</html>
<-- test1.html -->
<html>
<head>
<meta name="AUTHOR" content="christophe barbé">
<base target="main">
</head>
<body>
<p>The URL in the browser should be index.html</p>
<p>Click <a href='test2.html'>here</a> to continue the test</p>
</body>
</html>
<-- test2.html -->
<html>
<head>
<meta name="AUTHOR" content="christophe barbé">
<base target="main">
</head>
<body>
<p>The URL in the browser should still be index.html</p>
<p>Click <a href='test1.html'>here</a> to go back</p>
</body>
</html>
Reproducible: Always
Steps to Reproduce:
1.Get the files index.html,test1.html,test2.html included in this bug report
2.Open the index.html file
3.Click on the link 'here'
Actual Results:
The URL is now test2.html
Expected Results:
The URL should still be index.html (note that it's a Chimera bug, Mozilla does
that correctly).
christophe, please attach your testcase to this bug using "Create a New
Attachment". Attach the frames first, then alter the FRAMESET to link to the
attached frame documents.
|
Reporter | |
Comment 2•23 years ago
|
||
|
|
Reporter | |
Comment 3•23 years ago
|
||
What you want seems difficult.
If you want I can send you the 3 files.
|
|
Reporter | |
Comment 4•23 years ago
|
||
If you want you can see the simple test case here:
http://cattlegrid.net/~christophe/chimera/
Confirmed using Chimera/2003021707. Revising Summary.
Note also that after going Back to the original document, the URL Bar still
doesn't show the FRAMESET URL.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: buggy target/frame interaction → URL Bar shows URL of loading FRAMEs, rather than remaining at the FRAMESET document
|
|
Reporter | |
Comment 6•23 years ago
|
||
You are right, the problem is simply the choice of the url to be displayed. The
frame content is correctly rendered.
The reason why I put the priority higher than normal is that it can cause a lot
of problem in dynamic web sites that rely on frame to hide the url parameters
and prevent users from reloading a already processed URL.
For example if the url is hidden.html?do=that and is hidden in a frameset
similar to my test case, the user should always see index.html and thus can't
reload hidden.html?do=that.
|
|
Reporter | |
Comment 7•23 years ago
|
||
The problem seems not to be the handling of the target property but instead a
problem in gecko.
I have field a bug against gecko:
http://bugzilla.mozilla.org/show_bug.cgi?id=195078
|
|
||
Comment 8•22 years ago
|
||
dupe
*** This bug has been marked as a duplicate of 195078 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
|
|
||
Comment 9•22 years ago
|
||
Excuse me? As the comments in bug 195078 say, the fact that this works in
SeaMonkey shows that the embedding app is probably doing something wrong. The
fact that multiple embedding apps are doing it wrong, doth not a Gecko bug make.
At the very least, please answer the questions I asked in bug 195078 about how
Camino gets the url in question.
You need to log in
before you can comment on or make changes to this bug.
Description
•