Closed
Bug 232895
Opened 21 years ago
Closed 20 years ago
named anchor containing (hash | pound | # | score) not linking properly
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: ebnf, Unassigned)
References
()
Details
Attachments
(1 file)
277 bytes,
text/html
|
Details |
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040115 Firebird/0.8.0+
The example page is very poorly formatted HTML, but it shows a strange linking
behavior.
<a href="foo.html# #123">foo</a>
to
<a name=" #123">
is what I expect to work, but Internet Explorer 6 SP1 works from <a
href="foo.html#123"> also, so pages get coded up this way. Maybe in quirks mode
allow this type of linking to work as well?
Reproducible: Always
Steps to Reproduce:
1. Visit page, click anchor link.
Actual Results:
Watch Moz/Firebird not follow the link.
Expected Results:
In strict mode, this is okay, but quirks I'd think this would work.
Comment 1•21 years ago
|
||
If someone could attach a simplified testcase here that could help in resolving
this, depending on what we want to do with this bug.
Comment 2•21 years ago
|
||
I believe the issue if that <a href="#foo" /> will link to <a name="#foo" /> in
IE... we've had bugs on this before and wontfixed them, iirc....
Whiteboard: DUPEME
(In reply to comment #2)
> I believe the issue if that <a href="#foo" /> will link to <a name="#foo" /> in
> IE... we've had bugs on this before and wontfixed them, iirc....
This "feature" is the only thing keeping a coworker of mine using IE. Should I
tell him to stick with it? Other than that, you can close this out if it's wontfix.
Works in IE6.0.28 but not in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.8a1) Gecko/20040520 or in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.6) Gecko/20040206 Firefox/0.8 or in Opera 7.23
Comment 5•21 years ago
|
||
That's because what IE does is just WRONG.
Comment 6•20 years ago
|
||
-> INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Comment 7•20 years ago
|
||
*** Bug 280948 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•