-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Switch ES spec URLs to multipage version #10615
Switch ES spec URLs to multipage version #10615
Conversation
Makes sense to prefer the multipage version for performance reasons. Blocked by having this in w3c/browser-specs, though. Edit: see w3c/browser-specs#299 |
This change switches all spec URLs from the ES spec to the multipage version of the spec at https://tc39.es/ecma262/multipage/ (rather than the single-page version). The changes were generated using the script at https://gist.github.com/sideshowbarker/9941751896b23b5465a0469f41255e3c
76a6694
to
d77742b
Compare
Since that’s now been merged — and tobie/specref#661 has too — it seems like this is ready to merge? |
Not ready yet. See mdn/yari#3893 for how orchestrating the different packages is a bit difficult. I need to improve this before we proceed. |
Ah, OK — so I’ve set this to Draft status to prevent it from getting merged prematurely |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! This is now ready and we should get it on MDN in this week's release to avoid having "Unknown specification" displayed for too long.
I've opened #10681 which attempts to add a test that requires us to always update to the latest specs that w3c/browser-specs require.
This change switches all spec URLs from the ES spec to the multipage version of the spec at https://tc39.es/ecma262/multipage/ (rather than the single-page version). The changes were generated using the script at https://gist.github.com/sideshowbarker/9941751896b23b5465a0469f41255e3c