RESOLVED CONFIGURATION CHANGED 81555
location.origin should be standardized or removed 
https://bugs.webkit.org/show_bug.cgi?id=81555
Summary location.origin should be standardized or removed
Boris Zbarsky
Reported 2012-03-19 13:52:16 PDT
This property doesn't seem to be present in the spec, and none of Gecko, Trident, Presto implement it....
Attachments
Add attachment proposed patch, testcase, etc.
Adam Barth
Comment 1 2012-03-19 15:58:46 PDT
Yeah, the spec is here, but I haven't done a good job of following through and driving this spec through the standards process: http://dvcs.w3.org/hg/url/raw-file/tip/Overview.html IMHO, origin is a useful property (and easy to implement).
Boris Zbarsky
Comment 2 2012-03-19 19:29:37 PDT
That's fine (and I agree that if defined clearly this is not hard to implement), but HTML5 isn't even using that URL spec for Location...
Ian 'Hixie' Hickson
Comment 3 2012-03-20 17:00:12 PDT
It will eventually, I just haven't updated HTML yet because the URL spec isn't solid enough yet.
Alexey Proskuryakov
Comment 4 2012-03-20 17:04:14 PDT
Looks like this bug should be closed at this point - it does not make sense to track HTML standard work in WebKit bugzilla.
Ahmad Saleem
Comment 5 2022-08-09 12:18:45 PDT
It seems that Webkit now support it: https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_loc_origin Also MDN show that Webkit / Safari support it since Safari 5.1: https://developer.mozilla.org/en-US/docs/Web/API/Location/origin I am going to mark this as "RESOLVED CONFIGURATION CHANGED", I tried to find bug about implementation from Webkit Github but I couldn't. If someone can find implementation bug, please mark it as "DUPLICATE of BugID". Thanks!
Ryosuke Niwa
Comment 6 2022-08-09 12:20:56 PDT
Yeah, this has been standardized awhile ago.
Note You need to log in before you can comment on or make changes to this bug.