-
Notifications
You must be signed in to change notification settings - Fork 313
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
Skip executing fetch handlers if it is no-op. #1674
Conversation
The previous flag name has negation in the flag name and I am afraid it is confusing. Let me rename it.
Since [=all fetch listeners are empty flag=] is used only if [=set of event types to handle=] contains "fetch". This actually does not change the behavior.
Some of the link-defaults were disguising bikeshed errors, making it ambiguous which terms from other specs need exporting. I've fixed those up, and will PR to the DOM spec to get those terms exported. |
PR to export the terms whatwg/dom#1170. However, this includes a term that's marked as "intentionally not exported", so we might need to find another way. |
Merging. Thanks for all the work on this @yoshisatoyanagisawa! |
SHA: 4b38437 Reason: push, by jakearchibald Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: 4b38437 Reason: push, by pull[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Following on from #1672
Preview | Diff