You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
Fixesmdn/browser-compat-data#16839
### Problem
If there is support without a prefix, altname, or flag, even if there is a note indicating a minor limitation with that support, don't show the symbol indicating the need fro a flag, altname, or prefix.
### Solution
Check for support without major limitations, not just support without limitations
What type of issue is this?
Incorrect support data (ex. Chrome says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
The compat data reports that Firefox requires the
-webkit
prefix forflex-basis
. It doesn't.What browsers does this problem apply to, if applicable?
Firefox
What did you expect to see?
Unprefixed support is okay.
Did you test this? If so, how?
Yes, using browserstack.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://developer.mozilla.org/en-US/docs/Web/CSS/flex-basis#browser_compatibility
Do you have anything more you want to share?
After seeing #7403, I think that the data may be correct, and this is really a UX issue. It appears as if Firefox requires a prefix.
MDN URL
No response
MDN metadata
No response
The text was updated successfully, but these errors were encountered: