1592911 - news.google.com ServiceWorker not successfully installing - Clicking links from Google News page makes the service worker remain in a “Registering” state and throwing several errors in browser console

Status: NEW

(Core :: DOM: Service Workers, defect, P3)

Description

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: sw_es10_0.gif

Affected versions

• 72.0a1 (20191030215116)

Affected platforms

• Windows 10x64
• macOS 10.14
• Ubuntu 18.04

Steps to reproduce

1. Open Firefox with a new profile and browser console.
2. Open about:debugging,click on “This Nightly tab” and observe the Service Workers section.
3. Go to news.google.com and click on a random link before the service worker is registered.

Expected result

• Service worker is successfully registered and there are no errors thrown in the console.

Actual result

• Service worker for new.google.com remains in registering state and disappears after a while and several errors are shown in the browser console.

Regression range

• I will search for one ASAP if there is one.

Additional Notes

• Attached a screen recording with the issue.
• Attached a .txt file that contains the errors from the browser console.
• Clicking on random link registers the service worker for Google News page and clicking again links from the page makes the service worker remain in “Registering” state repeating the actual result every time another link is clicked.

Comment 1

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: workers_error.txt

Adding the errors that are thrown in the browser console after Step 3 and after repeating Step 3.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Comment 3

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Hello! I tried searching for a regression range using dom.serviceWorkers.parent_intercept;true but it seems that the issue is reproducible way back to Firefox 62.0a1 (20180621220127) when the pref was introduced.
The issue is also reproducible on the builds before the pref (dom.serviceWorkers.parent_intercep) by following the about:debugging-> Workers until Firefox 48.0a1 (20160419030312). On the builds, past this date, the service workers are not staying registered at all. They appear and disappear. So I think it's safe to assume that this issue is not a regression.

Comment 4

[Andrew Sutherland [:asuth] (he/him)]

Thanks for the in-depth regression investigation there, that is useful to know. It's possible there's some kind of feature detection or something going on that we're failing. Dropping this to a P3 accordingly.