[webkit-dev] CSS filter behavior change - what is our policy?

Noam Rosenthal noam at webkit.org
Thu Mar 14 10:45:02 PDT 2013

How do we go about rendering behavior changes that affect features that are
enabled on shipping browsers?

I'm specifically referring to http://trac.webkit.org/changeset/139770
The brightness filter is enabled by default on chrome and Safari if I
remember correctly, and now pages that use brightness(0) would have their
element blackened, while before those elements would have been left
unchanged. This is of course "correct" so I can't claim it's a bug, but
still it would break existing websites, even if not many.

Do we see CSS filters as being "bleeding edge" enough where we don't care?
Do we have a way to warn web developers about this? They'd basically have
to check Chrome/Safari/Other version in order to work around the problem,
as there's no media query for "check if brightness behaves correctly".

Guidance appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20130314/1600baaf/attachment.html>

More information about the webkit-dev mailing list