document.origin is undefined rather than a DOMString

Issue #13018631 • Assigned to Kris K.

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”

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

    Sign in