Disable -moz-appearance for non-UA/chrome sheets
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | affected |
People
(Reporter: MatsPalmgren_bugz, Unassigned)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
(Keywords: dev-doc-needed, site-compat)
Comment 1•8 years ago
|
||
Updated•8 years ago
|
Comment 3•8 months ago
|
||
Having this causes at least one webcompat issue. I think having webkit prefixed one as an alias of moz prefixed one still allows us to have only the former, right?
Updated•8 months ago
|
Updated•7 months ago
|
Comment 4•7 months ago
|
||
(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #3)
Having this causes at least one webcompat issue. I think having webkit prefixed one as an alias of moz prefixed one still allows us to have only the former, right?
Well, kind of? As you noted, MozAppearance is used for UA sniffing, so the question is whether removing it would cause issues than it fixes.
Comment 5•7 months ago
|
||
We also need to account for pages using things like -moz-appearance: textfield to suppress number input spinners and so on... I did some github searching, and most "MozAppearance" in ... bits seem harmless, but pages would regress due to -moz-appearance: textfield. So maybe we need to remove it from the OM but keep parsing -moz-appearance?
Comment 6•7 months ago
|
||
By tweaking GenerateCSSPropListWebIDL.py? Works for me.
Updated•7 months ago
|
Description
•