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

How can we remember to update baseline status, dates, and browser versions of hard-coded features? #2364

Open
captainbrosset opened this issue Nov 29, 2024 · 0 comments

Comments

@captainbrosset
Copy link
Contributor

The following features have hard-coded baseline/browser statuses:

  • autofocus
  • avif
  • datalist
  • http2
  • http3
  • intersection-observer-v2
  • jpegxl
  • notifications
  • scroll-to-text-fragment
  • web-bluetooth
  • webdriver-bidi
  • webp

For example, scroll-to-text-fragment:

status:
  baseline: false
  support:
    chrome: "81"
    chrome_android: "81"
    edge: "83"
    safari: "16.1"
    safari_ios: "16.1"

Or, http2:

  baseline: high
  baseline_low_date: 2015-09-30
  support:
    chrome: "41"
    chrome_android: "41"
    edge: "12"
    firefox: "36"
    firefox_android: "36"
    safari: "9"
    safari_ios: "9"

Soon, we will also have notifications-app.yml (PR):

status:
  baseline: low
  support:
    chrome: 20
    chrome_android: 42
    edge: 14
    firefox: 22
    firefox_android: 22
    safari: 7
    safari_ios: 16.4

How can we remember to update the status when necessary?
The last example I pasted will soon need to move from low to high, and a baseline_high_date will be needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant