No indication of error when fetch event is aborted before the response body completes on navigations. |
||||||
Issue descriptionTest for this issue: https://crrev.com/2809083002 This test can simulate the situation where fetch(request) is lasting. When the worker handling the fetch event stops after registering the SW and opening 'slow test' on slow.html, the request for the main resource has failed correctly according to Network tab on the devtools. However, the loading animation is shown on the place of the favicon area and the reload button has not been back to the reload button (it's still X mark). I assume the main resource loading doesn't fail successfully though the network request has failed.
,
Apr 12 2017
Yes, I could reproduce it on M57 and M59.
,
Apr 12 2017
Ah, sorry. Yes means "yes, it has existed.".
,
Aug 3 2017
,
Aug 3
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 9
,
Jan 10
I looked at this again with the following steps: 1. Patch in https://chromium-review.googlesource.com/c/chromium/src/+/1404542 2. Run third_party/blink/tools/run_blink_httpd.py 3. Go to http://localhost:8000/serviceworker/tmp/slow.php 4. Open Network tab 5. Reload 6. Let the page load a little bit. Then go to DevTools -> Service Worker and stop the worker. I couldn't repro the wrong favicon and reload button. Actually the reverse seems to happen: it looks like the load finished fine with no indication otherwise. In non-S13nSW an ERR_CONNECTION_RESET appears in the console. But in S13nSW there's no error indication. I'm not really sure this is an error though. When you load a slow web page and hit "Stop", I think the page just stops loading however far it got, no? If that's accurate, maybe there's nothing to do here.
,
Jan 10
On second thought, I think this is unlikely to matter and the original bug doesn't seem to happen anymore so marking WontFix. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by falken@chromium.org
, Apr 12 2017