document.origin is undefined rather than a DOMString

Won’t fix Issue #13018631

Details

Author
Gerald R.
Created
Jul 31, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Standard affected
W3C DOM4

Found in build #
15.15063
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

document.origin is undefined when document is served from a file or a local server.

DOM4 spec says it should be a readonly attribute DOMString origin.

When run from Chrome, it evaluates to null (for file:) or a DOMString URL (for HTTP server).

See also

https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12236493/

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “Kris K.”

      Changed Title from “document.origin is undefined rather than a DOMString” to “document.origin is undefined rather than a DOMString”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Won’t fix”

    • We are in the process of attempting to remove document.origin from the WHATWG DOM specification. The reason being that the current implementations are not interoperable and it is confusing to have both this and self.origin. The recommended approach is to use self.origin, and Edge will implement that in an upcoming release. 

      You can find out more information at https://github.com/whatwg/dom/issues/410#issuecomment-356662611

    You need to sign in to your Microsoft account to add a comment.

    Sign in