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

web-features baseline status is not sync'd with BCD #11366

Open
3 tasks done
captainbrosset opened this issue Jun 26, 2024 · 4 comments
Open
3 tasks done

web-features baseline status is not sync'd with BCD #11366

captainbrosset opened this issue Jun 26, 2024 · 4 comments
Assignees
Labels
browser-compat issues related to the browser compatibility data tables (BCD) idle p2 We want to address this but may have other higher priority items. plus:baseline

Comments

@captainbrosset
Copy link
Contributor

Summary

On https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set/difference#browser_compatibility, compare the BCD table and baseline status:

Capture d’écran 2024-06-26 à 07 45 32 Capture d’écran 2024-06-26 à 07 45 58

The method became available in Firefox 127, therefore making it "baseline low".

However, Yari uses 0.8.6 of web-features, which is 2 weeks old and which, indeed, shows Firefox as missing.

This is not Yari's fault because there hasn't been a new release of web-features since then, but I'm opening the issue here because this is where it manifests for users. We should discuss about the release cadence for web-features, and the strategy for yari to bump the version it depends on.

Pinging @ddbeck on this.

URL

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set/difference

Reproduction steps

  1. Open the page
  2. Look at the Baseline banner
  3. Look at the BCD table

Expected behavior

The banner, and BCD table, should always match.

Actual behavior

They differ.

Device

Desktop

Browser

Firefox

Browser version

Stable

Operating system

Mac OS

Screenshot

No response

Anything else?

No response

Validations

@github-actions github-actions bot added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Jun 26, 2024
@pransh15 pransh15 added the browser-compat issues related to the browser compatibility data tables (BCD) label Jun 26, 2024
@pransh15
Copy link

Hello @captainbrosset 🫡
Thanks for submitting this. I've been following the conversation on Mastodon, and I'll share this with the team.

@pransh15
Copy link

I have an update! We are aware of the issue and are discussing tackling it in the coming days. 🙌

@captainbrosset
Copy link
Contributor Author

web-features 0.9.0 is now available: https://github.com/web-platform-dx/web-features/releases/tag/v0.9.0.
Updating to it should fix the issue on MDN.

@caugner caugner added plus:baseline p2 We want to address this but may have other higher priority items. and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Jul 2, 2024
@caugner
Copy link
Contributor

caugner commented Jul 2, 2024

This is somewhat related to #6488.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser-compat issues related to the browser compatibility data tables (BCD) idle p2 We want to address this but may have other higher priority items. plus:baseline
Projects
None yet
Development

No branches or pull requests

4 participants