| Summary: | location.origin should be standardized or removed | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Boris Zbarsky <bzbarsky> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | abarth, ahmad.saleem792, ap, arv, bfulgham, gsnedders, ian, rniwa, syoichi |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Boris Zbarsky
2012-03-19 13:52:16 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). 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... It will eventually, I just haven't updated HTML yet because the URL spec isn't solid enough yet. Looks like this bug should be closed at this point - it does not make sense to track HTML standard work in WebKit bugzilla. 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! Yeah, this has been standardized awhile ago. |