This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/multipage/semantics.html Multipage: https://html.spec.whatwg.org/multipage/#following-hyperlinks Complete: https://html.spec.whatwg.org/#following-hyperlinks Referrer: https://html.spec.whatwg.org/multipage/ Comment: Append the hyperlink suffix to the URL before resolving Posted from: 81.82.104.124 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0
Appending a string to a URL doesn't make sense
It seems to actually be appended to the end though, as if the URL were a string. E.g., test <a href="?test#test"><img ismap src=image></a> in the Live DOM Viewer. It's not entirely clear to me how we can fix this without breaking blob URLs and such.
I guess we could specify this as either appending to the fragment (if non-null) or the query (if non-null), and otherwise setting the query to it. It's rather weird behavior, but okay... Domenic, thoughts on that?
I have a hard time understanding this issue from the brief description, but isn't this something that should be entirely determined by existing browser behavior? I can't get the test from comment #2 to show me any kind of URL, but I assume you're saying the result is "?test#test?123,456". In which case your algorithm sounds reasonable, although I don't think "setting the query" works given that the suffix contains a "?" already.
Existing browsers don't always use URL objects, which create problems for blob URLs. Maybe we should give up on blob URLs ever working correctly though. However, that's probably a larger issue and as far as I can tell we can fix this without addressing that.
https://github.com/whatwg/html/issues/4484