Return null origin of "blob:" URL containing inner non-"http(s):" URL

[rmisev]

Fixes: #770.

• [x] At least two implementers are interested (and none opposed):
  • Chromium
  • Gecko
  • WebKit
• [x] Tests are written and can be reviewed and commented upon at:
  • https://github.com/web-platform-tests/wpt/pull/40133
• [x] Implementation bugs are filed:
  • Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1448562
  • Gecko: Bug 1834703
  • WebKit: https://bugs.webkit.org/show_bug.cgi?id=257262
  • Deno: https://github.com/denoland/deno/issues/19241
  • Node.js: https://github.com/nodejs/node/issues/48157
• [x] MDN issue is filed: N/A

(See WHATWG Working Mode: Changes for more details.)

---

Preview | Diff

[annevk]

@ricea @zcorpan thoughts?

[zcorpan]

This seems OK to me. cc @valenting

[valenting]

This makes sense to me. I filed Bug 1834703 - Return null origin of "blob:" URL containing inner "blob:" URL for Firefox changes. Thank you for the tests.

[annevk]

@ricea to be clear, all browsers have failures here. E.g., "Origin parsing: <blob:file://host/path> without base" yields !EQ("null", "file://") in Chromium. (Same for ftp, ws, and wss.)

@rmisev do you want to file the remaining implementation bugs?

[ricea]

@ricea to be clear, all browsers have failures here. E.g., "Origin parsing: blob:file://host/path without base" yields !EQ("null", "file://") in Chromium. (Same for ftp, ws, and wss.)

I am okay with that.

[rmisev]

@rmisev do you want to file the remaining implementation bugs?

@annevk, I think you would fill in the bug reports faster than me.