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: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html Multipage: http://www.whatwg.org/C#the-history-interface Complete: http://www.whatwg.org/c#the-history-interface Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Shouldn't it throw a SyntaxError if resolving the URL fails? Posted from: 90.230.218.37 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.19 Safari/537.36 OPR/19.0.1326.9 (Edition Next)
The reason I made it throw a SecurityError is that it allows implementors more flexibility in deciding how to implement the checks here. If we are specific about which different exceptions are fired in which order, it becomes harder to get it right, easier to have bugs, and yet we don't gain much. Also, it's arguable a reasonable exception -- the security error is that the URL isn't in the same origin as the original URL, something which is trivially true if the URL isn't parsable. Does that make sense?
Yeah, OK.
Marking WONTFIX per comment 2.