Daniel D. Beck

@pygy For context, this PR is meant to regularize a process we already do here, so I don't think introducing new criteria is in scope. But for completeness, I'll say...

@caugner that is an interesting example! I have a few thoughts on this: First, in an earlier draft (before I submitted the PR), I had a caveat about how the...

We discussed this on a special double-length BCD call today. Main takeaways: - I need to make it explicit that this guideline describes situations where `partial_implementation` is _required_, but not...

This came up again in the BCD call today. I've applied a few changes: - Added a first attempt at a developer significance requirement here as "The browser's support has...

From today's BCD call: this still needs a link to this PR, for symmetry with other guidelines. I'll try to get to this shortly.

I think this is only partly fixed. It looks like Chromium and WebKit might use `font-variant-position` when the font contains the required glyphs, but fails to synthesize them when the...

> ([@ddbeck](https://github.com/ddbeck) Re. the [hypothetical guidelines](https://github.com/mdn/browser-compat-data/pull/26605#issuecomment-2838278224), would you set partial for a CSS property that is broken in Firefox only for SVGs?) I wouldn't in this specific case, mostly because...

So I think mirroring misled me a bit on the review of the PR resolving this issue. It's still looking pretty weird over on web-features: https://github.com/web-platform-dx/web-features/blob/173fd86d21e464560e7bec51bcd3ac93dd9d4d7d/features/form.yml.dist#L16-L60 The mirroring script seems...

> We should enforce that, so that we can make the guarantee that BCD will always report a real (non-ranged) version for as many years as possible. Agreed. Though I'd...

This isn't resolved by #27068. That PR moves the rolling window to five years, not 1 January 2020.