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

CSS spec names have become "Unknown specification" #20772

Closed
myakura opened this issue Sep 15, 2022 · 7 comments · Fixed by mdn/yari#7262
Closed

CSS spec names have become "Unknown specification" #20772

myakura opened this issue Sep 15, 2022 · 7 comments · Fixed by mdn/yari#7262
Labels
Content:CSS Cascading Style Sheets docs

Comments

@myakura
Copy link
Contributor

myakura commented Sep 15, 2022

MDN URL

https://developer.mozilla.org/en-US/docs/Web/CSS/width

What specific section or headline is this issue about?

Specifications

What information was incorrect, unhelpful, or incomplete?

The name of the specification is "Unknown specification".

What did you expect to see?

For this particular page, it should be "CSS Level 2" (or CSS2).

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Page report details
@github-actions github-actions bot added Content:CSS Cascading Style Sheets docs needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Sep 15, 2022
@myakura
Copy link
Contributor Author

myakura commented Sep 15, 2022

I just saw that the links are updated to use csswg-drafts GitHub pages.
mdn/browser-compat-data@085deec
That may have broken the spec name matching...?

@myakura
Copy link
Contributor Author

myakura commented Sep 15, 2022

Ah, perhaps w3c/browser-specs#706 will solve the issue?

@Elchi3
Copy link
Member

Elchi3 commented Sep 16, 2022

Ah, perhaps w3c/browser-specs#706 will solve the issue?

Partially, yes. I guess we still need to implement looking for the alternateUrls property if it gets introduced in that PR.

I don't know when the issues with drafts.csswg.org will be resolved and BCD changes back to these URLs. So, maybe we need to go down the alternateUrls route, but the browser-specs PR seems like a prerequisite here.

@Elchi3
Copy link
Member

Elchi3 commented Sep 16, 2022

cc @queengooborg @sideshowbarker

@queengooborg
Copy link
Collaborator

This will be tracked in mdn/yari#7173!

@queengooborg queengooborg removed the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Sep 16, 2022
@Josh-Cena
Copy link
Member

Closing in favor of mdn/yari#7173 since it doesn't seem actionable on the content side

@sideshowbarker
Copy link
Member

FYI for the record here — it looks like we now have an upstream solution, per w3c/browser-specs#704 (comment):

Browser-specs now lists https://w3c.github.io/csswg-drafts/ URLs for CSS specs under the nightly.alternateUrls.

So it seems we can fix this by updating our browser-specs client/consumer code to check the nightly.alternateUrls value in addition to the nightly and nightly.url values.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Content:CSS Cascading Style Sheets docs
Projects
None yet
6 participants
@sideshowbarker @Elchi3 @myakura @queengooborg @Josh-Cena and others