Re: Intent to ship '-webkit-appearance' and changes to '-moz-appearance' values

[Mike Taylor]

Hi Jonathan,

On 8/7/18 5:16 PM, Jonathan Watt wrote:
> Summary
> -------
>
> I plan to enable the pref in Nightly builds (using EARLY_BETA_OR_EARLIER) to
> turn on the '-webkit-appearance' alias for '-moz-appearance'. This pref
> simultaneously changes the behavior of the 'menulist-button' value, and shortly
> the 'button-bevel' value.
>
> 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.

From the "Possible ways forward" from that link, I think option 5 makes
the most sense. We can always spec this in the Compat Standard, if the
issue is never resolved.

> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1480073
>
> Preferences: layout.css.webkit-appearance.enabled
>
> Platfrom coverage: All
>
> Estimated release: 63 (tentatively)
>
> Known webcompat impact: 19 out of 20 of the open -webkit-appearance
> webcompat.org issues are fixed by this change.

This is very cool. Thanks for fixing sites for our users! We'll keep an
eye out for weird regressions.

--
Mike Taylor
Web Compat, Mozilla

[Jonathan Watt]

Hi Mike,

On 08/08/2018 16:31, Mike Taylor wrote:
> Hi Jonathan,
>
> On 8/7/18 5:16 PM, Jonathan Watt wrote:
>> Summary
>> -------
>>
>> I plan to enable the pref in Nightly builds (using EARLY_BETA_OR_EARLIER) to
>> turn on the '-webkit-appearance' alias for '-moz-appearance'. This pref
>> simultaneously changes the behavior of the 'menulist-button' value, and shortly
>> the 'button-bevel' value.
>>
>> 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.
>
> From the "Possible ways forward" from that link, I think option 5 makes
> the most sense. We can always spec this in the Compat Standard, if the
> issue is never resolved.

That's the option that I think makes most sense too, although I'd like to see if
we can convince Google to remove some of their infrequently used values from the
Web. In that case it seems like there would be some value in supporting a new
value to allow resetting the property.

>> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1480073
>>
>> Preferences: layout.css.webkit-appearance.enabled
>>
>> Platfrom coverage: All
>>
>> Estimated release: 63 (tentatively)
>>
>> Known webcompat impact: 19 out of 20 of the open -webkit-appearance
>> webcompat.org issues are fixed by this change.
>
> This is very cool. Thanks for fixing sites for our users! We'll keep an
> eye out for weird regressions.

Much appreciated, thank you. :)

Jonathan