W3C home > Mailing lists > Public > public-fx@w3.org > April to June 2014

Re: [compositing-1] please move non-separable effects to Level 2

From: Dean Jackson <dino@apple.com>
Date: Fri, 18 Apr 2014 22:38:16 -0700
Cc: Rik Cabanier <cabanier@gmail.com>, FX <public-fx@w3.org>
Message-id: <ED73E883-8D00-41E0-AC74-D15214EF72BB@apple.com>
To: robert@ocallahan.org

On 18 Apr 2014, at 10:15 pm, Robert O'Callahan <robert@ocallahan.org> wrote:

> On Sat, Apr 19, 2014 at 12:55 PM, Dean Jackson <dino@apple.com> wrote:
> So youre objecting to a subset of features being removed that you havent shipped, have not announced any plans to support,
> The full set of operators is implemented in Gecko and I don't see any barriers to enabling them in release builds. We don't have compositor support, which means some use-cases would be slow, but I think most use-cases won't be affected by that and everything should work.

We support them in software mode too, just not in compositing mode. Since we dont want to have blending disappear if an element becomes composited (99.9% of developers would not be able to explain all the cases in which this could happen), wed only ship an implementation that supports them everywhere.

So this is our implementation feedback, which I think is one of the main reasons for CR. If other implementers disagree and they remain in the spec, then ok. It would be nice to know how much usage these modes see in tools, or what effects will be impossible on the Web without them.


Received on Saturday, 19 April 2014 05:38:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:49 UTC