Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

I feel like about:serviceworkers is already broken in Nightly, is that expected?

It is expected to be broken, yes. It asks the ServiceWorkerManager in whatever process it is in for the list of ServiceWorkers. With parent-intercept (dom.serviceWorkers.parent_intercept) enabled, only the parent process ServiceWorkerManager knows anything. Bug 1456995 enabled it on nightly. So in the content processes, they think there are no ServiceWorkers.

The options are:

• Remove about:serviceworkers
• Change the about module bits to remove URI_CAN_LOAD_IN_CHILD and URI_MUST_LOAD_IN_CHILD at https://searchfox.org/mozilla-central/rev/652014ca1183c56bc5f04daf01af180d4e50a91c/docshell/base/nsAboutRedirector.cpp#103

This bug is not a Fission MVP blocker.

Andrew, do you want to fix this about:serviceworkers bug for Fission now or just fix bug 1273821 (remove about:serviceworkers and redirect to about:debugging#workers)?

Given that about:debugging is not available on Android, I would prefer if we kept (and fixed) about:serviceworkers.

(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) (he/him) from comment #7)

Given that about:debugging is not available on Android, I would prefer if we kept (and fixed) about:serviceworkers.

Works for me!

The parent is where the info is in the parent process. Without this fix,
about:serviceworkers misleadingly suggests there are no Service Workers
present at all. This is desired for mobile.

https://hg.mozilla.org/mozilla-central/rev/bf05a0b449d8