Engineer on @googlechrome. Involved in CSS and W3C standards. Previously @mozilla, @w3ctag. Mastodon: @dbaron@w3c.social
Rockville, Maryland, USA
Joined March 2008
- Tweets 7,521
- Following 1,244
- Followers 4,296
- Likes 18,519
He managed to end an inordinate number of explanations with "so it all comes down to zoning in the end."
Sounds like the theme of Ed Glaeser's intermediate microeconomics course that I took 14 years ago.
1
1
Seems like Edge is right, Firefox is wrong (break not ok there), and Chrome is wrong (float placed higher than allowed)
1
3
Careful -- next we'll have companies trading in collateralized technical debt obligations, then a mortgage crisis.
3
There was a later change to remove the dropdown from the without-system-theme version, for compat with other browsers.
1
In Fx33, <select> w/ & w/o -moz-appearance:none are different (use system theme vs. not, general behavior of appearance).
3
So we end up having to copy different behaviors from other browsers at different times. @supports won't help there.
2
1
The 'appearance' property specifically is a mess; there's no spec for form controls or how 'appearance' affects them.
1
You can't test for a specific effect that it has, only whether it's accepted, which should mean it does something (it did)
1
I think the issue you're seeing is that we've had to add more behaviors to -moz-appearance:none, copying other browsers.
1
-moz-appearance:none has been supported since before @supports. filter:blur(5px) new in bugzil.la/1057180 (Fx35)
Today's @FirefoxNightly supports 'unicode-bidi: isolate', 'isolate-override', and 'plaintext', without prefixes developer.mozilla.org/en-US/…
1
8
16
Photos from vacation last month in Switzerland & France: flickr.com/photos/dbaron/set…
1
5