246356 - Error: uncaught exception: Load of #a denied.

Status: RESOLVED INACTIVE

(Core :: DOM: Core & HTML, defect, P5)

Description

[timeless]

biesi says there's no nsIURI for some of these cases.

Steps:
1. click the url link
2. click 'b'

Expected results:
see "hi"

Actual results:
Error: uncaught exception: Load of #a denied.

Experienced while using commercial code from 1.7b ish. biesi tested a simpler
version presumably using trunk.

Comment 1

[Jason Bassford]

The "b" does not even have a hyperlink for me, so clicking it does nothing at
all.  Using 6/10-08 under XP.

Comment 2

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

oh, don't let that fool you... look in the javascript console

Comment 3

[Boris Zbarsky [:bzbarsky]]

The "data" protocol does not really support fragment identifiers in the current
implementation (and arguably per spec).  The fact that they work on initial load
is a bug in the content sink.

Comment 4

[Darin Fisher]

(In reply to comment #2)
> oh, don't let that fool you... look in the javascript console

I did... and I likewise do not see an anchor getting rendered.  There is no
output in the Javascript console.  I'm testing "Mozilla/5.0 (X11; U; Linux i686;
en-US; rv:1.7) Gecko/20040603 Firefox/0.8.0+"

Comment 5

[timeless]

for my reference i still see this behavior in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041123

(no, i don't expect the bug to go away on its own, but some people have
expressed their inability to experience the bug)

Comment 6

[Andrey Melnikov]

WORKSFORME in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050331 Firefox/1.0+

"b" isn't rendered as a link (which is per spec, as comment #3 says), and
clicking it produces nothing in JS console.

Can anyone confirm this with recent builds?

Comment 7

[Wayne Mery (:wsmwk)]

which is it - is this a real bug, or is bz correct that this is working per spec?