| Summary: | Clicking a link for a fragment scroll in a document with <base target="_blank"> opens in a new tab | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Brady Eidson <beidson> | ||||||||
| Component: | Page Loading | Assignee: | Brady Eidson <beidson> | ||||||||
| Status: | RESOLVED INVALID | ||||||||||
| Severity: | Normal | ||||||||||
| Priority: | P2 | ||||||||||
| Version: | 528+ (Nightly build) | ||||||||||
| Hardware: | All | ||||||||||
| OS: | All | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Brady Eidson
2015-06-03 09:21:15 PDT
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. Created attachment 254187 [details]
Test case (ready to be a layout test if this is actually a bug)
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. Created attachment 254188 [details]
Both main frame and iframe test
And just for posterity, I had an iframe version of the test as well.
Created attachment 254189 [details]
Both main frame and iframe test
For posterity, iframe version of the test as well.
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. |