On 08/08/2018 21:08, Boris Zbarsky wrote: > On 8/7/18 6:16 PM, Jonathan Watt wrote: >> Spec: None. We're reverse engineering Chrome and ignoring >> https://drafts.csswg.org/css-ui-4/#appearance-switching >> since the 'appearance' property defined there is not >> web compatible. > > Are we writing down something that could get turned into a spec?
I've got a bunch of messy notes that I hope will be of some use for that, but no, so far I have not attempted to create draft spec text to replace the text in CSS UI 4. To be frank the behavior of '-webkit-appearance' in Chrome/Safari is so inconsistent and messy that would be a ton of work. I think it would make most sense to start by trying to get Google to remove some of their infrequently used values from the Web to reduce the amount of spec work that's needed. It would also help a great deal to restrict the elements that individual '-webkit-appearance' values can be applied to, since spec'ing all the weird and wonderful edge case permutations would be a waste of time. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
