106912 - Anchors with HREF="" are wrongly treated as link to current page (invalid)

Status: VERIFIED INVALID

(Core :: DOM: HTML Parser, defect)

Description

[Stellan Klebom]

Anchors with HREF="" are wrongly treated as link to current page

Assume we have a page "xxx/yyy.html" containing anchor <a href="">.

That anchor really should link to "xxx/". Mozilla links to "xxx/yyy.html"

IE, Netscape 4 and 6 all links to "xxx/" as the RFC 1808 suggests.


-------------------------------------------------------
RFC 1808 Relative Uniform Resource Locators  June 1995

5.2.  Abnormal Examples

   Although the following abnormal examples are unlikely to occur in
   normal practice, all URL parsers should be capable of resolving them
   consistently.  Each example uses the same base as above.

   An empty reference resolves to the complete base URL:

      <> = <URL:http://a/b/c/d;p?q#f>

Comment 1

[timeless]

.

Comment 2

[Christopher Hoess (gone)]

Bug is self-contradictory. Based on the text quoted below, our behavior is
correct (i.e., href="" links to the full base URL, which in the document at
"http://www.example.com/xxx/yyy.html" is "http://www.example.com/xxx/yyy.html").
Resolving INVALID.

Comment 3

[Moied]

Verified invalid

Comment 4

[Vadim Berezniker]

*** Bug 136740 has been marked as a duplicate of this bug. ***

Comment 5

[Chris Casciano]

I was in the process of testing this on various browsers for bug 136740 when it
got duped and figured I'd post this info for future reference. With the test
case at : http://placenamehere.com/Mozilla/linktest.html

Broswers that think href="" is the current document:
Mozilla 0.9.9/ Win & OS X
Opera 6/PC
IE5.1.3/OS X
Opera 5b/OS X
OmniWeb 4.1b2/OS X
iCab2.7.1/OS X
Lynx 2.8.3rel.1/OS X

Broswers that think href="" is the current folder:
IE6/PC
NN4.77/PC
NN4.75/OS X

Note from the test that the following is also true - all browsers tested above
do link to the current directory in the second and third links, so if that's
what a web developer is trying to do I would suggest using one of those. (myself
I always use "./").

Comment 6

[John Levon]

*** Bug 116221 has been marked as a duplicate of this bug. ***

Comment 7

[Josh Birnbaum]

*** Bug 201378 has been marked as a duplicate of this bug. ***

Comment 8

[Jesse Ruderman]

*** Bug 323069 has been marked as a duplicate of this bug. ***

Comment 9

[Jesse Ruderman]

*** Bug 323168 has been marked as a duplicate of this bug. ***

Comment 10

[Jesse Ruderman]

*** Bug 263980 has been marked as a duplicate of this bug. ***

Comment 11

[:Gavin Sharp [email: [e-mail]]]

*** Bug 339112 has been marked as a duplicate of this bug. ***

Comment 12

[:Gavin Sharp [email: [e-mail]]]

*** Bug 265799 has been marked as a duplicate of this bug. ***

Comment 13

[:Gavin Sharp [email: [e-mail]]]

*** Bug 272203 has been marked as a duplicate of this bug. ***

Comment 14

[:Gavin Sharp [email: [e-mail]]]

*** Bug 310951 has been marked as a duplicate of this bug. ***

Comment 15

[:Gavin Sharp [email: [e-mail]]]

*** Bug 321090 has been marked as a duplicate of this bug. ***

Comment 16

[Boris Zbarsky [:bzbarsky]]

*** Bug 339112 has been marked as a duplicate of this bug. ***

Comment 17

[Phil Ringnalda (:philor)]

*** Bug 337727 has been marked as a duplicate of this bug. ***

Comment 21

[Christian :Biesinger (don't email me, ping me on IRC)]

Boris, how is this a duplicate? That bug is about images whereas this one is about anchors.

Comment 22

[Boris Zbarsky [:bzbarsky]]

Er, indeed.  It looks like people were dumping all empty-URI-reference related issues here...  <sigh>.