Re: [url] Added inScope static (#22)

> I'm not sure what you mean here? Why would CORS come into play when comparing URLs?

I'm just trying to be thorough.  Ruling out CORS makes things simpler, so that's good.  Now lets be thorough from the other direction: I'll note that this isn't a byte-for-byte comparison, but rather a comparison of the values of individual URL components *after parsing*.  At the moment, there is still quite a bit of [variety](https://url.spec.whatwg.org/interop/test-results/) as to how user agents parse URLs.  At a minimum, this merits a cautionary note.  A more aggressive stance would be to return false for all [non-conforming](https://specs.webplatform.org/url/webspecs/develop/#url-writing) inputs.  That's still not perfect, but adding more conformance checks may be easier to get consensus on than to get implementation movement towards interop on non-conforming inputs.  It is also easier to lift a restriction later than it would be to add one.

> Probably need to move this to a larger forum once a concrete proposal is ready. I'm happy to do that once the PR is ready.

I thought this was a concrete proposal.  I'm willing to merge it, and then make editorial changes on top of it.  The one thing I'm holding on is either an indication that @annevk doesn't object, or an indication that browser vendors will implement this anyway.

---
Reply to this email directly or view it on GitHub:
https://github.com/webspecs/url/pull/22#issuecomment-68140693