Bug 145607 – Clicking a link for a fragment scroll in a document with <base target="_blank"> opens in a new tab

• Component: Page Loading
• Status: RESOLVED INVALID

[Brady Eidson]

Clicking a link for a fragment scroll in a document with <base target="_blank"> opens in a new tab (in Safari)
 
I noticed this while fixing https://bugs.webkit.org/show_bug.cgi?id=145580

Unlike the broken cases in 145580, this one is not a regression - It's been around for as long as I can tell.

[Brady Eidson]

Attaching a test case.

This actually happens in both Chrome (not too surprising) and Firefox (much more surprising)

So it *might* not be a bug. Need to research the <base> element.

[Brady Eidson]

Created attachment 254187 [details]
Test case (ready to be a layout test if this is actually a bug)

[Brady Eidson]

IE does this too.

So it's not weird from a compat standpoint.

Just weird from an expectational standpoint.

I'll try to read up on <base> at some point in the future, but won't explore any further for now.

[Brady Eidson]

Created attachment 254188 [details]
Both main frame and iframe test

And just for posterity, I had an iframe version of the test as well.

[Brady Eidson]

Created attachment 254189 [details]
Both main frame and iframe test

For posterity, iframe version of the test as well.

[Brady Eidson]

The spec is pretty clear about this - Clicking a link with a <base target=""> element in place should open the URL in the target browsing context (in this case new), even if there's a fragment identifier.

Got it.