W3C home > Mailing lists > Public > public-fx@w3.org > October to December 2011

Re: [css-shaders] GLSL implementation defined limits

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 11 Nov 2011 15:07:24 -0800
Message-ID: <CAAWBYDATFy1Q70QaK=eEez8YQ_P+Xe3ZCmWMpBnFNUDxk=4WoA@mail.gmail.com>
To: Chris Marrin <cmarrin@apple.com>
Cc: Vincent Hardy <vhardy@adobe.com>, "Gregg Tavares (wrk)" <gman@google.com>, "public-fx@w3.org" <public-fx@w3.org>
On Fri, Nov 11, 2011 at 3:02 PM, Chris Marrin <cmarrin@apple.com> wrote:
> True, but I'm not sure we can solve every problem that this brings up. There are other places in CSS where properties work together to get a desired effect and if they're not all supported you get something less than useful. I think there needs to be a more general CSS solution for that problem. What I was trying to do was to give authors the ability to use more complex shaders and still work everywhere. I can imagine many cases where the fallback shader can be made to do enough of the effect to make it look right in combination.

We *are* solving the generic problem with the @supports rule.
Unfortunately, I don't think that would help Gregg's use-case. :/

Received on Friday, 11 November 2011 23:08:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 June 2015 03:33:46 UTC