Un-range values creating (new) uncertainty following mirroring changes

[ddbeck]

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

Due to #24155, several features in web-features have newly uncertain Baseline dates. It looks like all of the affected features are caused by ranged values for Firefox (desktop) from the following keys:

• css.properties.display.table-caption
• css.properties.dominant-baseline (and descendants?)
• css.properties.background-size.auto
• css.properties.fill-opacity
• css.properties.stroke-opacity
• svg.global_attributes.fill-opacity
• svg.global_attributes.stroke-opacity

It would be nice to avoid these ranges, as they prevent the calculation of a single date for whole groups of keys.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

Unranged values.

Did you test this? If so, how?

N/A

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

• Fix mirroring from upstream to downstream with ranges #24155
• Bump @mdn/browser-compat-data from 5.6.21 to 5.6.22 web-platform-dx/web-features#2409 (review)

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response

Tasks

Beta Give feedback

1. css.properties.display.table-caption
2. css.properties.dominant-baseline (and descendants?)
3. css.properties.background-size.auto
4. css.properties.fill-opacity
5. css.properties.stroke-opacity
6. svg.global_attributes.fill-opacity
7. svg.global_attributes.stroke-opacity

[ddbeck]

For web-features, moving the ranges back to Firefox 39 or earlier would also be acceptable (as we can't ever produce a date before Edge 12's release). For example, CSS.supports("display", "table-caption") seems to return true as far back as Firefox 13 but the result would be inconclusive before that.

[caugner]

@ddbeck This should be resolved now, see PRs auto-referenced above.

[ddbeck]

Brilliant, thank you!

[ddbeck]

Actually, it turns out that I was wrong about the browsers involved (I misread the dates involved). It looks like I need to resolve the dates for Chrome and Safari too.

@caugner what test cases did you use for these? Are you in a position to run them on very old Chromes and Safari as well?

[ddbeck]

Ohh, sorry I got ahead of myself. It looks like this was mostly Bugzilla spelunking?

[caugner]

It looks like this was mostly Bugzilla spelunking?

@ddbeck Yes, for Firefox I looked at Bugzilla and the Mozilla source code. If you have small visual examples for those features, I can add them to https://github.com/caugner/bcd-examples/, and test them with early Chrome versions locally (via CrossOver) and Safari (via BrowserStack Live).