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

Allow alternate nightly spec URLs #7262

Merged
merged 1 commit into from
Oct 13, 2022

Conversation

queengooborg
Copy link
Collaborator

Within the last few releases, a pull request was merged to BCD that replaces links to drafts.csswg.org with w3c.github.io/csswg-drafts. This was done because drafts.csswg.org is almost always unavailable, leaving MDN readers (including and especially contributors) with no spec to refer to. The downtime issues have persisted for over a year, with no end in sight. Because of this, various developers have created their own mirrors with reliable build engines, including https://andreubotella.com/csswg-auto-build/, whose code was then used to create a new official mirror.

As an unfortunate result, however, any spec URLs using the new mirror will show "Unknown specification". This has been resolved in browser-specs by adding a new alternateUrls property that contains the URL to the mirror. This PR taps into this new property, resolving the "unknown specification" issue.

This fixes #7173 and fixes mdn/content#20772. This closes #7175 as irrelevant.

@queengooborg
Copy link
Collaborator Author

Note: the failing test is unrelated to this PR and can be dismissed.

@schalkneethling schalkneethling added the p1 We will address this soon and will provide capacity from our team for it in the next few releases. label Sep 28, 2022
Copy link
Collaborator

@sideshowbarker sideshowbarker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’ve tested this and found that it works as expected without regressing anything or causing any failures or unexpected behavior. And from code inspection, this pretty clearly seems to be the right fix.

@sideshowbarker
Copy link
Collaborator

Is there any strong reason that we shouldn’t go ahead and merge this PR?

Especially is there any strong reason to further delay on it relative to the harm the problem is continuing to cause for MDN readers who’ve been seeing “Unknown specification” for all CSS specs for an entire month now?

The change in this PR can’t make anything worse than the current “Unknown specification” situation. And it’s not a change that requires a huge amount of scrutiny; the solution here seems pretty straightforward — and it’s hard to imagine there being any way to improve upon what’s already in the patch in this PR.

Copy link

@schalkneethling schalkneethling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @queengooborg and apologies for the long wait. 💯

@schalkneethling schalkneethling merged commit 29366f9 into mdn:main Oct 13, 2022
@queengooborg queengooborg deleted the spec-urls-alternatenightly branch October 13, 2022 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p1 We will address this soon and will provide capacity from our team for it in the next few releases.
Projects
Development

Successfully merging this pull request may close these issues.

CSS spec references show as "Unknown specification" CSS spec names have become "Unknown specification"
3 participants