W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: [css4-images] Color stop syntax

From: Dirk Schulze <dschulze@adobe.com>
Date: Mon, 15 Oct 2012 19:20:12 -0700
To: Rik Cabanier <cabanier@gmail.com>
CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <21C9D9B4-23DB-4E6B-B93A-5007019F72B9@adobe.com>
To the order of stop color and stop offset. If Lea run into this problem on a live demo, it also means that browsers don't allow switching the order. If we change the spec here, it will most likely incompatible with current browsers (as long as they don't implement it). I wonder if we may not have enough tests for CSS3 Images. And if it changes, it may should go into CSS3 Images before it gets recommendation and not in CSS4 Images.

Greetings,
Dirk

On Oct 15, 2012, at 6:14 PM, Rik Cabanier <cabanier@gmail.com> wrote:

> On Mon, Oct 15, 2012 at 6:06 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
>> On 09/23/2012 07:20 AM, Lea Verou wrote:
>>> 
>>> Itís only a pair now, in the future it might be extended to allow for more
>>> things.
>>> For example, Rik Cabanier recently suggested in a discussion we had that
>>> it might
>>> be useful to allow an optional midpoint, like Adobe products traditionally
>>> supported.
>>> Of course, in that case, a specific relative order would be necessary,
>>> since they
>>> would both be of the same type.
>> 
>> 
>> I want to suggest handling that as a color stop without a specified color,
>> and having that mean 'average the two colors before/after me'. That *is*
>> equivalent to having a "midpoint", isn't it?
>> 
> 
> That is correct. Woud that syntax be backward compatible?
> What happens today if you don't specify a color?
> 
Received on Tuesday, 16 October 2012 02:20:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:01 GMT