Hi, scenario checked with today's (6/29) master build in Nightly Debug (eaf4f9b45117 revision) STRs: 1- open about:sw in a tab (no sw is shown which is correct) 2- register a sw 3- change the sw 4- go to about:sw tab (the sw is properly shown), then, click on the update button Actual result: Nothing happens Expected result: The update process is properly initiated and completed Notice that the update process properly work with the following STRs: 1- register a sw 2- open about:sw in another tab (the sw is properly shown) 3- change the sw 4- click on the "update" button within about:sw tab

Hi, I've checked update process with today's master build (7/9) (f34a7120f46b revision) in Nightly Debug under a e-10s scenario and the behavior has changed a bit: STRs: 1- open about:sw in a tab (no sw is shown which is correct) 2- register a sw 3- change the sw 4- go to about:sw tab (the sw is properly shown), then, click on the update button Actual result: Nothing happens Expected result: The update process is properly initiated and completed The same result in case of registering the sw first and then opening about:sw. Currently, it is necessary to close the browser and launch it again in order to be able to properly launch the update process through about:sw.

Hi just checked with m-c Nightly Debug (c95ebeebbc5d revision) and the update process is launched under e10s scenario although the activate event is fired even when the sw is controlling the client, which shouldn't. It seems we should wait for SWM refactor (Bug 1182117), setting the corresponding dependency.

Note that we're hoping to migrate all users of about:serviceworkers to about:debugging. See bug 1220747.

Andrew - are we ever going to fix this? If not, we should wontfix and promote about:debugging.

Let's focus on about:debugging.