Pinging this old thread since nothing seems to have happened since it was last discussed.
My recommendation is still to make location.origin return the "origin of the document" rather than "the origin of the URL". I would be surprised if that didn't fix many more pages than it broke. I think making the location object match URLUtils is futile. There's so much weirdness about the location object that I think we should treat it as the special flower that it is. That would also make the origin available to workers. I don't have a strong opinion on if we also implement document.origin or not. / Jonas On Wed, Dec 3, 2014 at 9:02 AM, Anne van Kesteren <ann...@annevk.nl> wrote: > On Wed, Dec 3, 2014 at 7:58 AM, Boris Zbarsky <bzbar...@mit.edu> wrote: >> Indeed. Bringing us back to "why would someone ever care about the latter?" > > I don't think you should use that unless you want to know the origin > of the URL of the corresponding href in question. E.g. similar to why > you might want to inspect <a>.origin. I realize that people use > Location objects for all sorts of things that might be wrong, I don't > have a good solution to that other than that we should not build more > on top of it. Location is fundamentally a broken object, due to it > representing a document's browsing context's active document. > > > -- > https://annevankesteren.nl/ > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
