Alex Christensen

If I understand this correctly, this is intended to return true if this is a same page "navigation", right? I'm confused by all this same page "navigation" measurement stuff. Don't...

This does need fixing. I oppose the first option. The third option seems most like what we do with other cross-origin timing exposure.

I don't think it would be a big deal to change Safari to say "other" here

Unable to reproduce the iOS test failure after several attempts in different configurations. cq+

My initial thought is that we already have a way for a server to expose its timing information, and if the server chooses not to expose that information we should...

If I've understood this correctly, this seems to only change behavior when decoding "invalid" input. I would like to believe that most content comes from valid encoders, so I would...

Given that all browsers agree on behavior, I think we should change the spec to match behavior in this case

I guess I don't have a strong opinion here. I don't think there will be a lot of compatibility issues if we change this.

Should we at least update the tests to be consistent with the current specs? I also found that http://wpt.live/html/browsers/history/the-location-interface/location-protocol-setter-non-broken-weird.html and http://wpt.live/url/url-setters-a-area.window.html also contradict each other.

I think I'm ok with aligning Safari with Chrome and Firefox. Aside: Our tests really need to check each ASCII code point and a few other code points in each...