Add Baseline regression notes #3187
Conversation
github-actions
bot
added
the
feature definition
| # TODO: https://github.com/web-platform-dx/web-features/issues/1971 | ||
| # Status changed: https://github.com/web-platform-dx/web-features/pull/2358, https://github.com/web-platform-dx/web-features/pull/2491 | ||
| # 2024-12-19 — low → false — Regressed status to match Caniuse, which considers support beginning at BYOB shipping. | ||
| # 2025-01-30 — false → high — Split BYOB into a separate "readable-byte-streams" feature. Linked that one to Caniuse. | ||
| # References: | ||
| # - https://caniuse.com/streams |
There was a problem hiding this comment.
I fussed over this for a while and ended up deciding to omit the note entirely. The first note would say that the feature regressed, the second note would be some new category (advance? unregression?) showing that we more or less reverted the second note. It seemed to me that the correct course of action in that scenario would be to withdraw the note, so that's what I've done.
ddbeck
added
package:web-features
schema
features/content-visibility.yml
Outdated
| - category: baseline-regression | ||
| date: 2025-01-30 | ||
| message: > | ||
| The `content-visibility` feature regressed from newly available to limited availability. |
There was a problem hiding this comment.
For any kind of extraordinary status change, it might also be useful to the tools consuming this info to encode it into the note:
old_status: low
new_status: falseThere was a problem hiding this comment.
Good suggestion. I've made changes along these lines with fccb850. It also meant that I could drop boilerplate text from each message.
This is a work in progress toward fixing #1971.
This structures the existing Baseline regression comments as notes. I'm looking for early feedback on whether this structure for notes would be useful.