- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Fri, 18 Apr 2014 17:15:24 +1200
- To: Dean Jackson <dino@apple.com>
- Cc: FX <public-fx@w3.org>
- Message-ID: <CAOp6jLbBP3bUj9sF0TDOvFGQKtRhzUaaeY-WbKsdm8wuKJrtkg@mail.gmail.com>
On Fri, Apr 18, 2014 at 8:42 AM, Dean Jackson <dino@apple.com> wrote: > As of https://trac.webkit.org/r167448 WebKit supports mix-blend-mode > unprefixed. > > We did this knowing that we will be unable to implement the non-separable > modes in the near future (hue, saturation, color and luminosity). We > suggest these be moved to Level 2 of the specification. > > If they are not moved, we’ll probably put the prefix back on, because we > don’t want to ship a non-prefixed incorrect implementation. > I don't see why this is necessary. If there are values you don't support, so be it ... that doesn't mean the entire property needs to be prefixed*. As soon as those values are present in a level 2 spec, in practice you'll be back to exactly the same situation you're in now. * Or better still, disabled. Prefixes hurt the Web. Can you point to an explanation of why Webkit prefers prefixes over the Gecko/Blink approach of user-accessible flags to enable/disable experimental features? Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w
Received on Friday, 18 April 2014 05:15:52 UTC