Opaque Response Blocking

[hsinyi]

Request for Mozilla Position on an Emerging Web Specification

• Specification Title: Opaque Response Blocking
• Specification or proposal URL (if available): https://github.com/annevk/orb
• Explainer URL (if available):
• Caniuse.com URL (optional):
• Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1532642
• Mozillians who can provide input (optional): @zcorpan @sefeng211 @farre

Other information

• There's a PR open which has the actual changes to the Fetch spec: Define opaque-response blocking  whatwg/fetch#1442
• ORB has been enabled on Nightly and early beta on Firefox.
• Chrome's intent-to-ship for ORB v0.1 and v0.2
• Also see Fetch: CORB #81 (comment)

[sefeng211]

I think it is worth noting that we've found a few issues in the spec that may not be web-compatible, such as Fetch API raising errors. However, given we've implemented this and starting to roll this out, it should be an easy positive from us.

[martinthomson]

Agreed and marking this positive. @sefeng211, let me know if you would prefer to put this on a dashboard (it doesn't seem big enough to warrant that).

[farre]

Since ORB to some extent (but not wholly) replaces CORB, and CORB is on the dashboard it might make sense to include ORB there as well. And even though ORB spec-wise is small it is fairly impactful.

@hsinyi, @sefeng211 do you agree?

[hsinyi]

Second @farre's points.

[farre]

Not sure if I managed to ask for dashboard before @martinthomson closed it, sorry for the ping :D

[martinthomson]

If one of you want to open a pull request to put the update in place, we can reopen this one to track that. But we don't need an issue to make that change.