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

2018-08-16 Thread Eric Shepherd (Sheppy)
Those notes should also be useful for the docs team if we need to document this stuff before it makes it into a spec. On Wed, Aug 15, 2018 at 6:18 PM Mats Palmgren wrote: > On 8/14/18 12:52 AM, Jonathan Watt wrote: > > On 08/08/2018 21:08, Boris Zbarsky wrote: > >> Are we writing down something

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

2018-08-15 Thread Mats Palmgren
On 8/14/18 12:52 AM, Jonathan Watt wrote: On 08/08/2018 21:08, Boris Zbarsky wrote: 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 replac

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

2018-08-15 Thread Jonathan Watt
Regarding criteria for letting -webkit-appearance ride the trains, I assume you're wondering about that due to my use of EARLY_BETA_OR_EARLIER to flip the pref. That was mostly because Mats has been away on summer vacation and I suspect that he'll want to have input on whether this is ready to ship

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

2018-08-15 Thread Mats Palmgren
The plan to ship -webkit-appearance looks good to me, fwiw. On 8/14/18 12:46 AM, Jonathan Watt wrote: > On 08/08/2018 16:31, Mike Taylor wrote: >> On 8/7/18 5:16 PM, Jonathan Watt wrote: >>> Spec: None. We're reverse engineering Chrome and ignoring >>> https://drafts.csswg.org/css-ui-4/#a

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

2018-08-15 Thread Jonathan Watt
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.

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

2018-08-15 Thread 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 >> simult

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

2018-08-08 Thread Boris Zbarsky
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

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

2018-08-08 Thread 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 short

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

2018-08-07 Thread Chris Peterson
Awesome! This should fix some common webcompat issues for Firefox/GeckoView on Android. What are the criteria for letting -webkit-appearance ride the trains? The GeckoView team is eager to ship mobile webcompat fixes, so they might be willing to accept more risk than Firefox desktop. Are the

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

2018-08-07 Thread Jonathan Watt
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