I would like to revive this intent. At this point estimated release
would be 54, and Blink has shipped this a while ago.
The state of things here is as follows:
1) location.origin still exists and sites use it, so we can't remove
it. But we can deprecate it if we want.
2) document.origin is in the spec and shipping in Safari and Chrome.
Except the Safari version doesn't match the spec at all...
https://bugs.webkit.org/show_bug.cgi?id=168022 filed. Edge 14 doesn't
seem to support this; I don't know about their developer preview.
3) The spec also defines self.origin (in both workers and windows, for
consistent API). For the window case it returns the origin of the
active document. No one else implements this yet; I will be sending a
separate intent for this.
-Boris
On 12/1/14 10:09 AM, Boris Zbarsky wrote:
Summary: document.origin returns the Unicode serialization of the
document's origin. The returned value does not depend on what
document.domain was set to.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=931884
Spec: http://dom.spec.whatwg.org/#dom-document-origin
Platform coverage: All of them.
Estimated release: 37
I don't plan to put this behind a pref. It's trivial to back out if
need be.
Blink is considering implementing this too, and they're trying to find
out whether we plan to implement. I think this is a useful feature and
we should add it.
The only caveat is possible confusion due to the difference between
document.origin and location.origin; I'm a bit torn about what to do
about that, if anything, short of removing location.origin....
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
