URL constructor origin "null" for all non http(s) uris

Fixed Issue #8644531


Patrick K.
Aug 25, 2016
This issue is public.
Fixed in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

execute the following javascript

new URL(‘ftp://example.com’).origin

note the result

Originally reported by Andrew Betts on twitter (https://twitter.com/triblondon/status/768705390691307520), all other compliant browsers return "ftp://example.com", as per specification. We only return an origin for http and https uris. Blob, WebSocket, FTP, File, SSH, gopher, and any other URI mentioned in the URL Standard results in “null” being returned.

As noted by Ada Rose Edwards (https://twitter.com/Lady_Ada_King/status/768725459555278849) in that thread, this is particularly egregious because we are returning "null’ - not a literal null, but a string with the value “null” , which is truthy.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Patrick K.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “Brad E.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “Eugene V.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Eugene V.” to “Sanket J.”

      Changed Assigned To from “Sanket J.” to “Nishant S.”

      Changed Status from “Confirmed” to “Fixed”

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

    Sign in