- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Sun, 13 Dec 2015 08:56:53 -0800
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Florian Rivoal <florian@rivoal.net>, Daniel Holbert <dholbert@mozilla.com>, Dean Jackson <dino@apple.com>, "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
On Sat, Dec 12, 2015 at 8:57 AM, 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. Because supporting them is on the same level of "do this or pages don't work" as any other property. A browser that expects to be [i]actually used[/i] has to support these; pussyfooting around with weaker language doesn't help anyone. > '-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. Yes it does break things, or else FF and IE wouldn't feel pressured to support it. For example, white text on a gradient background without a background-color can completely disappear when you lack gradient support. (I accidentally did this on my website at first!) ~TJ
Received on Sunday, 13 December 2015 16:57:42 UTC