-
Notifications
You must be signed in to change notification settings - Fork 69
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
Some CSS properties/types have issues with values #1181
Comments
I'm afraid that you're going to have a hard time relying on the Depending on the spec, this may be:
Ideally, the specs would be more explicit about values that a property can take. In some cases, the fix is easy because the spec already goes through the values and all that is needed is a bit of extra markup. In many cases though, more editorial work is needed. We haven't tried to push in that direction yet. That would be the right "upstream" ;) In short, the CSS extracts only appear to contain what you're looking for, but the |
I have been working on a big update to the mdn-bcd-collector project to parse values directly out of enumerated types, so that the collector is able to better track new CSS property values when specifications update.
However, I've noticed that there are a number of properties and types that do not define all of the applicable values:
display
property (css-display
spec)values
entries for any of the enumerated types (ex.<display-outside>
)display
property (mathml-core
spec)values
entry for themath
value<layout-box>
,<paint-box>
,<coord-box>
(css-box
spec)values
entries for the enumerated types they build on<counter-style>
(css-counter-styles
spec)values
entry for<counter-style-name>
outline-style
property (css-ui
spec)values
entry for<outline-line-style>
font-size-adjust
property (css-fonts-5
spec)values
entry,ex-height | cap-height | ch-width | ic-width | ic-height
, that should be separatedFor now, we're working around the problem with a manually curated list, but it'd be helpful if these type values were included upstream!
The text was updated successfully, but these errors were encountered: