Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

responseReady getting rejected does not mean the background fetch failed. #130

Open
mugdhalakhani opened this issue Nov 29, 2018 · 1 comment

Comments

@mugdhalakhani
Copy link

responseReady could fail if the response stream errored (maybe due lost of network connectivity). It shouldn't be equated to the background fetch failing, instead, the response should be retried by calling match() again to get a new record, and a new responseReady promise.

Can we call this out somewhere in the spec please?

@jakearchibald
Copy link
Collaborator

Yeah, makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants