W3C home > Mailing lists > Public > www-style@w3.org > December 2015

Re: [lots] -webkit prefixed properties and values

From: Florian Rivoal <florian@rivoal.net>
Date: Sun, 13 Dec 2015 08:47:01 +0900
To: Brad Kemper <brad.kemper@gmail.com>
CC: Daniel Holbert <dholbert@mozilla.com>,"Tab Atkins Jr." <jackalmage@gmail.com>,Dean Jackson <dino@apple.com>,"L. David Baron" <dbaron@dbaron.org>,www-style list <www-style@w3.org>
Message-ID: <757CB4D2-24ED-4323-9729-07219F7AE2D1@rivoal.net>


On December 13, 2015 1:57:51 AM GMT+09:00, Brad Kemper <brad.kemper@gmail.com> wrote:
>
>
>> On Dec 10, 2015, at 7:31 PM, Florian Rivoal <florian@rivoal.net>
>wrote:
>> 
>> Isn't that what are are suggesting: specify and deprecate means
>browsers must support (which they do), AND authors must not use.
>
>Why MUST? I think "here are some legacy proprietary properties that you
>can support if you want for increase web compat" is enough. 

Isn't that the same with any property? If you don't mind some incompatibly, anything can be skipped. But here, all existing UAs have found they needed to implement (and nobody likes to do this, so the decision is typically not taken lightly). 

>'-webkit-gradient' had graceful fallback. It wouldn't break the web if
>some really old pages had a flat background in the title bar instead of
>perfectly emulating the gradient of the title bar of the iPhone 1's UI
>title bar. 

It does break. Quite a few of these same pages have white text on that gradient background. Remove the background, and you get white on white.

And it's not just "some really old pages". The mobile web is full of WebKit only sites. I don't have data at hand anymore, but last I checked I believe this was far from a marginal problem.

----
- Florian Rivoal
Sent from my phone. Please excuse my brevity
Received on Saturday, 12 December 2015 23:47:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:59 UTC