-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Synchronize with BCD v5.5.14 #32594
Synchronize with BCD v5.5.14 #32594
Conversation
@@ -53,7 +53,7 @@ The `hanging-punctuation` property may be specified with one, two, or three spac | |||
|
|||
### Values | |||
|
|||
- `none` | |||
- `none` {{experimental_inline}} |
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.
However also it looks like the script here is marking every value of the property experimental, rather than the main property itself. That doesn't seem right.
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.
The bot simply mimics BCD. It's a bug in BCD:
The property should be marked experimental in BCD then the bot will reflect it in the page baner.
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.
- submitted a fix in BCD: Fix a bug in
hanging-punctuation
property status browser-compat-data#22568
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.
Asking the question again which got wrongfully made in review comment below.
@Elchi3 why the hanging-punctuation
property was made non-experimental and not its values? At least one value should've been non-experimental right?
@@ -32,31 +32,31 @@ margin-trim: unset; | |||
|
|||
### Values | |||
|
|||
- `none` | |||
- `none` {{experimental_inline}} |
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.
Here again, if the property itself is experimental, why mark all the values experimental?
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.
Technically, because BCD tracks it like that: all the values have a separate status tracked.
The bot simply mimics the BCD i.e. track property(page header) and values(inline badges) separately.
Pros of separate tracking:
- Keeps the implementation simple. Keeps BCD the single source of truth.
- Third party scraping tools won't have to be intelligent too. Many popular IDEs use MDN snippets as it is in tool tips.
- Readers landed from search engines directly on the property won't have to scroll up to see if it's experimental.
- Reviews will become complex as in localised diff a value, that remained experimental after the property becomes non experimental, will look like going non-experimental to experimental.
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.
Note that this is different from the decision that was made about secure context: https://github.com/orgs/mdn/discussions/482#discussioncomment-7796301. Why are we inconsistent here?
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.
Why are we inconsistent here?
Does the inline secure context discussion and decision apply to all the inline macros? Putting this in weekly meeting agenda.
7d7bc94
to
9dac6d6
Compare
browser-compat: css.properties.content-visibility | ||
--- | ||
|
||
{{CSSRef}}{{SeeCompatTable}} | ||
{{CSSRef}} |
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.
Here and in many other cases, the main property is not marked experimental, but all its values are. What does this mean?
@@ -35,7 +35,7 @@ The keyword value `normal`, or a `<number>` optionally followed by an `<integer> | |||
|
|||
### Values | |||
|
|||
- `normal` | |||
- `normal` {{experimental_inline}} |
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.
Here, the main property is marked experimental, but not all its values are.
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.
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.
This is a BCD issue.
Not sure what this has to do with initial-letter.
@Elchi3 why the property was made non-experimental and not its values? At least one value should've been non-experimental right?
The initial-letter property is supported in Chrome and Safari, so it is not experimental. (although, given it is only supported with a prefix in Safari, one could argue). The normal
property is likely also supported in Safari and not just Chrome, so this is the bug in BCD. Maybe @queengooborg did not take into account prefixes when adding CSS property values?
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.
Prefixes are not tracked by the mdn-bcd-collector, so any prefix-based data was recorded manually. I've just submitted mdn/browser-compat-data#22596 to correct the Safari data for the normal
value.
In regards to the experimental status, actually, the initial-letter
property is accurately marked as experimental. Per the experimental status guidelines, prefixes are basically ignored when picking an experimental status. Experimental should be set to false
if Chrome and Safari both supported the property without a prefix; in this case, only one browser does.
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.
Not sure what this has to do with
initial-letter
.
Ohh, the statement was for the hanging-punctuation
. The comment accidentally got made in the review box below (here).
However, mdn/browser-compat-data#22596 made it confusing for the initial-letter
property. It is experimental but its value(s) are not. 😕
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.
The comment accidentally got made in the review box below (here).
?? My comment here was for initial-letter
, and it is that the property is marked experimental at the top level, but not all its values are. I don't understand this. If the property is experimental "as a whole", how can it have values that are not experimental?
hanging-punctuation
has a different issue, that I've also commented on, which is that it is not marked experimental at the top level, but all its values are. If all its values are experimental, how does it make sense for the property itself to be not experimental?
- : The inline contents are aligned to the right edge of the line box. | ||
- `center` {{deprecated_inline}} {{non-standard_inline}} | ||
- `center` |
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.
justify-all
is marked as experimental in this one but missing in the BCD table.
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.
The property doesn't exist in the BCD code.
@@ -38,7 +38,7 @@ text-decoration-skip: unset; | |||
|
|||
### Values | |||
|
|||
- `none` | |||
- `none` {{experimental_inline}} |
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.
Property is marked experimental, not all values are.
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.
BCD doesn't cover all the values here. The page author(s) should've have added these to BCD. Or we should have some mechanism to report these in BCD.
- : The text is justified by adding space between words (effectively varying {{cssxref("word-spacing")}}), which is most appropriate for languages that separate words using spaces, like English or Korean. | ||
- `inter-character` | ||
- `inter-character` {{experimental_inline}} | ||
- : The text is justified by adding space between characters (effectively varying {{cssxref("letter-spacing")}}), which is most appropriate for languages like Japanese. | ||
- `distribute` {{deprecated_inline}} |
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.
Property is not marked experimental, all values are except this one, which is not listed in BCD.
@@ -32,7 +32,7 @@ view-timeline-inset: 20% 200px; | |||
|
|||
Allowed values for `view-timeline-inset` are: | |||
|
|||
- `auto` | |||
- `auto` {{experimental_inline}} | |||
- : If set, the corresponding {{cssxref("scroll-padding")}} (or equivalent longhand value) for that edge of the scrollport is used. If this is not set (or set to `auto`), the value will usually be 0, although some user agents may use heuristics to determine a different default value if appropriate. | |||
- {{cssxref("length-percentage")}} |
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.
Property is marked experimental but this value isn't.
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.
The value doesn't exist in BCD.
@@ -26,7 +26,7 @@ view-transition-name: none; | |||
|
|||
- {{cssxref("custom-ident")}} |
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.
Property is marked experimental but this value isn't.
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.
The value doesn't exist in BCD.
Pinging BCD maintainers those who have worked on CSS props recently @queengooborg @hamishwillee @Elchi3
|
This pull request has merge conflicts that must be resolved before it can be merged. |
Closing in favour of #32835 |
BCD release v5.5.14
/cc @queengooborg @sideshowbarker