Open
Bug 1636315
Opened 3 years ago
Updated 3 years ago
Don't list compatibility issue when issue is avoided or mitigated
Categories
(DevTools :: Inspector: Compatibility, enhancement)
DevTools
Inspector: Compatibility
Tracking
(Not tracked)
NEW
People
(Reporter: sebo, Unassigned)
References
(Blocks 1 open bug)
Details
If a compatibility issue is solved by providing alternatives or fallbacks, the issue shouldn't be listed in the panel or only those browsers that are not covered them.
Examples:
- If
column-gap
is used together withgrid-column-gap
in a CSS rule for grid layout, basically all browsers are covered, so it neithercolumn-gap
(as not supported by all browsers) norgrid-column-gap
(deprecated) should be listed. - If
background-clip
and-webkit-background-clip
are specified in a CSS rule, all browsers are covered and they shouldn't be listed. - If
width: max(20vw, 200px);
is specified together withwidth: 20vw
andmin-width: 200px;
, the latter two cover older browsers while the former declaration covers the newer ones, somax()
shouldn't be listed. (It isn't anyway, but that's because of bug 1636301.)
Of course those rules would have to be created and maintained manually and may quickly get complicated, though this ensures that only valuable information is shown to authors and avoids cluttering the UI.
Sebastian
Updated•3 years ago
|
Type: defect → enhancement
You need to log in
before you can comment on or make changes to this bug.
Description
•