-
Notifications
You must be signed in to change notification settings - Fork 47
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
Is "Efficient Script Yielding" a relevant spec? #306
Comments
My sense is that the spec is no longer being worked on (its repo has in fact been archived), and is unlikely at this point to gain further implementation, so I don't think it should be added to browser-specs, and probably doesn't need to be referenced from MDN/BCD. |
Thanks, removing references to it then 👍 |
@Elchi3 asked me to comment here since I think we should keep the links in mdn/browser-compat-data#10746. The way I've been thinking about browser-specs so far is as a list of specs that browser implementers might want to look at, and I've used it in https://foolip.github.io/day-to-day/ as a way to take the temperate on spec development. So I actually think it's fine that browser-specs has dropped this spec, it's not something browser vendors need to care about. MDN/BCD however documents things that web developers might want to care about and only removes things that have been removed for over two years. This is a mismatch. Since the BCD entries in question are heading for eventual removal (after 2022-01-15, two years after the Edge 79 release) I think a reasonable solution is to just allow exceptions to the "must be in browser-specs" rule. |
https://w3c.github.io/setImmediate/
It appears in our dataset due to these pages:
https://developer.mozilla.org/en-US/docs/Web/API/Window/clearImmediate#specifications
https://developer.mozilla.org/en-US/docs/Web/API/Window/setImmediate
Is it a relevant spec or should we avoid referencing it from MDN/BCD?
The text was updated successfully, but these errors were encountered: