Skip to content

Conversation

@LeoMcA
Copy link
Member

@LeoMcA LeoMcA commented Sep 15, 2025

Opening as draft so this isn't merged without the corresponding fred change: nothing should break if we merge it before, but according to my local diff we'll have 4 baseline high banners appear where we'd want a discouraged banner instead.

Relates to: mdn/fred#654

Allows data for discouraged features to be included in our index.jsons, while maintaining the same asterisk logic as before: a discouraged feature is treated as having no baseline status. Without the asterisk logic change, the font page loses its asterisk.

@LeoMcA LeoMcA changed the title fix(baseline): include data for discouraged features feat(baseline): include data for discouraged features Jan 15, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 15, 2026

a593f82 was deployed to: https://rari-pr311.review.mdn.allizom.net/


static FEATURE_MDN_URLS: LazyLock<IndexMap<&'static str, &'static str>> = LazyLock::new(|| {
[
("async-clipboard", "/docs/Web/API/Clipboard_API"),
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

We've been talking about how best to maintain the web-feature <--> mdn mapping: once we've decided (and implemented) that, I'm sure we'll be able to add an mdn field to web-features.

Perhaps for these "features pointed at by discouraged features" it makes sense to add them manually in the web-features repo though

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

Successfully merging this pull request may close these issues.

2 participants