Closed groovecoder closed 1 year ago
Yeah, good point @groovecoder. Collapsing them wouldn't be too hard, but is it possible that it would allow inaccurate results? (Possibly related: #15)
There's a broader question here of how prefixed properties like this should be reported in general. Maybe a vendor-prefixed property should only produce a warning for that vendor's browser: e.g., a -moz-
property would only produce a warning if Firefox is one of the browsers being tested.
@anandthakker Any updates on this issue and feature ?
@ncoden I haven't made progress on it myself, but would gladly accept/support a PR!
Duplicate of https://github.com/anandthakker/doiuse/issues/91 ?
echo "body{-webkit-hyphens: none;
-moz-hyphens: none;
-ms-hyphens: none;
hyphens: none;
}" | npx doiuse --browsers "ie >= 8, firefox >= 2"
Now yields
<streaming css input>:4:1: CSS Hyphenation not supported by: IE (8,9), Firefox (2,3,4,5,3.5,3.6) (css-hyphens)
CSS:
doiuse
2.0.2 reports the same incompatibilities for each line:It would be much better to batch the identical report output to a single line that prints once after the block of prefix properties. So it looks more like this: