Bug 204064 – Navigating between domains with an active service worker blocks page load.

• Component: Service Workers
• Status: NEW

[Tor Brekke Skjøtskift]

Created attachment 383261 [details]
Navigation from ft.com to dagbladet.no and back to ft.com

Mobile Safari fails to load when a page on one domain with a service worker are visited for the second time after visiting a second page on a second domain with an active service worker. 

The request remains pending in the browser, but using a proxy we see that Mobile Safari is not sending the request to the server. 

The page will not load as long as the browser is open. The bug is still present if the page is opened in a new browser tab. 

If the browser is closed and the reopened, the page will load.

[Tor Brekke Skjøtskift]

We recreated this bug with two domains serving only the service worker registration code and empty service workers

[Tor Brekke Skjøtskift]

Created attachment 383263 [details]
Navigation from ba.no to dt.no and back to ba.no

This is our domains and we will remove the service worker for Mobile Safari until the bug is fixed. You will for this reason not be able to recreate this.

[Radar WebKit Bug Importer]

<rdar://problem/58674541>

[youenn fablet]

Hi Tor,
When you hit that issue, are all loads stalling on all pages?
If so, that might be the issue fixed by https://bugs.webkit.org/show_bug.cgi?id=206325.

[Tor Brekke Skjøtskift]

(In reply to youenn fablet from comment #4)
> Hi Tor,
> When you hit that issue, are all loads stalling on all pages?
> If so, that might be the issue fixed by
> https://bugs.webkit.org/show_bug.cgi?id=206325.

Yes, every page on the same domain stalls when this issue occurs.

When https://bugs.webkit.org/show_bug.cgi?id=206325 is released I will reintroduce the service worker in Mobile Safari and test.

We have removed the service worker from our domains, but I can still recreate the bug on Dagbladet www.db.no and ft.com if you need to test if the bug is fixed. Just visit www.db.no click on an article. Visit ft.com click on an article. Visit db.no again -> page wont load.

[youenn fablet]

> Yes, every page on the same domain stalls when this issue occurs.

What about other domains?

[Tor Brekke Skjøtskift]

(In reply to youenn fablet from comment #6)
> > Yes, every page on the same domain stalls when this issue occurs.
> 
> What about other domains?

Other domains loads. It is only pages on the domain with a service worker. When we testet on our domains ( we have about 80 publications), one domain did not affect other domains. But we had domains that stalled at the same time.

[youenn fablet]

This is probably not https://bugs.webkit.org/show_bug.cgi?id=206325.
I am not able to repro on a recent WebKit build.
Tor, on which version of iOS are you able to repro this?
Have you tried on the most recent version?

[Tor Brekke Skjøtskift]

(In reply to youenn fablet from comment #8)
> This is probably not https://bugs.webkit.org/show_bug.cgi?id=206325.
> I am not able to repro on a recent WebKit build.
> Tor, on which version of iOS are you able to repro this?
> Have you tried on the most recent version?

When we tested this in November/October we had an updated iPhone. This means the iOS version must have been 13.2.2 or 13.2.3. We also tried version 12, but I dont know the minor and patch version. I don't have a device here with me now, but I will test with an updated iPhone when I get to work tomorrow.
We are able to recreate the bug on Browserstack on iOS 13.2, 13.0 and 12.1

We have never managed to recreate the bug on emulators. Only real devices.

[youenn fablet]

Actually, I think I was able to repro it with a recent build.

[Tor Brekke Skjøtskift]

(In reply to youenn fablet from comment #10)
> Actually, I think I was able to repro it with a recent build.

Hi Youenn

I updated an iPhone to the latest iOS and could not reproduce the issue. I will try some more to see if I can trigger the bug. We will also set up an isolated test case tomorrow that will trigger the bug in Browserstack and see if we can reproduce it with the latest version of iOS.

[Tor Brekke Skjøtskift]

(In reply to Tor Brekke Skjøtskift from comment #11)
> (In reply to youenn fablet from comment #10)
> > Actually, I think I was able to repro it with a recent build.
> 
> Hi Youenn
> 
> I updated an iPhone to the latest iOS and could not reproduce the issue. I
> will try some more to see if I can trigger the bug. We will also set up an
> isolated test case tomorrow that will trigger the bug in Browserstack and
> see if we can reproduce it with the latest version of iOS.

(In reply to youenn fablet from comment #10)
> Actually, I think I was able to repro it with a recent build.

We enabled service worker on two test publications. 

In Browserstack with a real device, it is quite easy to replicate the issue.
The devices in Browserstack is on iOS 13.2 and are not updated to lates version of iOS.
UA on browserstack: "Mozilla/5.0 (iPhone; CPU iPhone OS 13_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1"

I cannot currently reproduce the issue on an updated iPhone (iOS 13.3). 

The domains where we enabled service worker are:
www.salsaposten.no and www.tangotidende.no
We reproduce the issue by visiting the front page and one article on each domain and alternating between them.