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

Synchronize with BCD v5.7.4 #38709

Merged
merged 2 commits into from
Mar 21, 2025
Merged

Synchronize with BCD v5.7.4 #38709

merged 2 commits into from
Mar 21, 2025

Conversation

OnkarRuikar
Copy link
Contributor

@OnkarRuikar OnkarRuikar requested review from a team as code owners March 19, 2025 01:10
@OnkarRuikar OnkarRuikar requested review from hamishwillee and wbamberg and removed request for a team March 19, 2025 01:10
@github-actions github-actions bot added Content:WebAPI Web API docs Content:HTTP HTTP docs size/s [PR only] 6-50 LoC changed labels Mar 19, 2025
Copy link
Contributor

github-actions bot commented Mar 19, 2025

Copy link
Member

@bsmth bsmth left a comment

Choose a reason for hiding this comment

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

Two suggestions to apply for inline statuses, but otherwise good to go.

For future us, it would be great to have "reason for change" somewhere, because it's not based on recently-changing support (X is now supported in Y browser in this bug), one is no longer categorized as experimental because of:

https://github.com/mdn/browser-compat-data/blob/main/docs/data-guidelines/index.md#setting-experimental

The feature has been supported by default and without major changes by some browser for two or more years.

And the other has a spec link added standard_track value changed. We have a link to release notes for BCD, but they don't list these kinds of changes (yet?).

Copy link
Collaborator

@hamishwillee hamishwillee left a comment

Choose a reason for hiding this comment

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

Looks good to me. Agree with @bsmth that a reason would be handy for some these changes (also that we should look at inline macro updates too)

Verified

This commit was signed with the committer’s verified signature. The key has expired.
danielleadams Danielle Adams
Co-authored-by: Brian Smith <brian@smith.berlin>
@OnkarRuikar
Copy link
Contributor Author

also that we should look at inline macro updates too

I don't know if we have a guideline for this, but using inline status macros in text is not a good idea. It's haaard to maintain. The bot can't reliably figure out which API/feature the member belongs to. For example, in the 'enabled' {{experimental_inline}} property is used for bla bla.. it is impossible to figure out if it is ABC.enabled or XYZ.enabled.
There are only <10 occurrences left and rest of the inline status macros have been used only in the lists(definition or normal ones).

@OnkarRuikar OnkarRuikar requested a review from bsmth March 21, 2025 04:01
@bsmth
Copy link
Member

bsmth commented Mar 21, 2025

Thanks, Onkar!

@bsmth bsmth merged commit 28da811 into mdn:main Mar 21, 2025
8 checks passed
@OnkarRuikar OnkarRuikar deleted the sync_bcd branch March 22, 2025 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:HTTP HTTP docs Content:WebAPI Web API docs size/s [PR only] 6-50 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants