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

Formal syntax wrong #28900

Closed
jimmonte opened this issue Sep 2, 2023 · 7 comments
Closed

Formal syntax wrong #28900

jimmonte opened this issue Sep 2, 2023 · 7 comments
Labels
Content:CSS Cascading Style Sheets docs

Comments

@jimmonte
Copy link
Contributor

jimmonte commented Sep 2, 2023

MDN URL

https://developer.mozilla.org/en-US/docs/Web/CSS/font-size-adjust

What specific section or headline is this issue about?

Formal syntax

What information was incorrect, unhelpful, or incomplete?

Formal syntax should optionally include ex-height | cap-height | ch-width | ic-width | ic-height

What did you expect to see?

See above

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

View link given on page for reference

Do you have anything more you want to share?

No response

MDN metadata

Page report details
@jimmonte jimmonte added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Sep 2, 2023
@github-actions github-actions bot added the Content:CSS Cascading Style Sheets docs label Sep 2, 2023
@wbamberg
Copy link
Collaborator

wbamberg commented Sep 2, 2023

This is because the algorithm we use to get the CSS syntax explicitly excludes numbered versions of the specs, and considers the unnumbered version to be the "current spec": mdn/yari#4656 (comment).

I'm not sure if this is a good policy or not, though, and it's unfortunate that the policy is different in BCD, which supplies the URL that appears in the "Specifications" section :(.

@wbamberg
Copy link
Collaborator

wbamberg commented Sep 2, 2023

I've started a discussion -> https://github.com/orgs/mdn/discussions/442

@OnkarRuikar
Copy link
Contributor

It doesn't matter in this case, just for info, we are stuck on an 9 month old version of @webref/css(v6.7.1) package:

@wbamberg
Copy link
Collaborator

wbamberg commented Sep 3, 2023

Yes, although as you say that is not relevant to this issue. I think it would be great if Yari extracted the csssyntax code to a separate package, and I have made a start at this in https://www.npmjs.com/package/query-css-syntax, which supports webref 6 and is what I am using for content embedding. But I don't know if Yari wants to do that.

@OnkarRuikar
Copy link
Contributor

I have made a start at this in npmjs.com/package/query-css-syntax, which supports webref 6

It would be really great if webref provided these easy retrieval APIs out of the box.

@bsmth
Copy link
Member

bsmth commented Sep 11, 2023

We are stuck on an 9 month old version of @webref/css(v6.7.1) package

There's a PR to upgrade to 6.0.0 here:

@Josh-Cena Josh-Cena removed the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Sep 30, 2023
@teoli2003
Copy link
Contributor

We discussed it today. We agree that this is a problem we want to solve, but it is a complex one. So, we are closing this but in favor of the discussion at https://github.com/orgs/mdn/discussions/442

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:CSS Cascading Style Sheets docs
Projects
None yet
Development

No branches or pull requests

6 participants