w3c / w3c/ServiceWorker

error handling for aborted streams feeding a navigation request

Open
#1,184 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
3.6k
Forks
324
Avg merge
14d 22h
Merged PRs (30d)
1

Description

This demo streams data every 1 second from a service worker infinitely:

https://html-sw-stream.glitch.me/

Chrome will currently eventually time out the service worker. When this happens the partially rendered iframe is just left.

Aside from the question in #1182, should aborting the service worker in the middle of the stream leave the partially rendered data? Should we not show an error here?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the streaming demo at https://html-sw-stream.glitch.me/ and read the related discussion in #1182. Reproduce the service-worker timeout during the stream, then determine whether the partially rendered iframe should remain or display an error; the issue names no repository file or test.

Written by the indexing model from the issue text.

Assessment

Domain
web-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.