302976 - Named anchors don't work in documents created with document.write

Status: NEW

(Core :: DOM: Navigation, defect)

Description

[Julien Lecomte]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Look at the attached test case. Tested using Firefox 1.0.6 and Deer Park Alpha 
2.

Reproducible: Always

Comment 1

[Julien Lecomte]

Attachment: Test case

Just click on the 'test' button, and then click on the link within the IFRAME.
Try the same operation in IE.

Comment 2

[Julien Lecomte]

If I set the src attribute of the IFRAME to an HTML document with such an 
anchor, it works well.

Comment 3

[zug_treno]

Related to bug 116680?

Comment 4

[Julien Lecomte]

It might be related to bug 116680, but bug 116680 does not appear to have been 
fixed, at least not in Firefox 1.0.6.

Comment 5

[Julien Lecomte]

Changing product. Firefox 1.5 Beta 2 still has this problem...

Comment 6

[Eugene Kim]

still reproducible in (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051215 Firefox/1.6a1 ...

Comment 7

[Jesse Ruderman]

Confirmed using Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060222 Firefox/1.6a1

Comment 8

[Jesse Ruderman]

Attachment: non-frame testcase

Comment 9

[Tom Ashworth]

I hate to bump a really old bug but, uh, this still isn't fixed. The first test case demonstrates it.

Tested in 16.0.1 and 17.0 on OS X Mountain Lion, and 16.0.2 on Windows 7. Bumping this after investigating this issue: https://github.com/remy/jsbin/issues/397

Comment 10

[Jeff Wagner]

Seeing this in Zimbra as well. Problematic for HTML emails that have anchor links.

Comment 11

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

One place to start debugging might be nsDocShell::ScrollToAnchor (docshell/base/nsDocShell.cpp), the things it calls, and the things that call it.  (See whether it's hit when expected, etc.)

Another place to start debugging might be that there's some dependency on the document URI being an instance of nsIURL, and in this case it might be only an nsIURI and not an nsIURL.  (That shouldn't be a factor even if it is the case, though.)

Comment 12

[Bundyo]

Additional workaround if someone needs it - I describe one here:
https://github.com/remy/jsbin/issues/589
It is a bit of a pain to implement, but the only workaround I have found so far.

Comment 13

[Christoph Reiter]

I can't reproduce this with Firefox 66.0.1 on Linux. Could it be that this was fixed?