W3C home > Mailing lists > Public > www-style@w3.org > August 2011

Re: [css3-images] Order of color-stop fixup

From: Shane Stephens <shans@google.com>
Date: Fri, 12 Aug 2011 04:54:38 -0700
Message-ID: <CAGTfzwS_3RBJnM-9yuVR15fr-RbSynR1Uq15T6eMWtDcrghNSA@mail.gmail.com>
To: Brian Manthos <brianman@microsoft.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
On Thu, Aug 11, 2011 at 10:46 PM, Brian Manthos <brianman@microsoft.com>wrote:

>  It seems unnecessary and error-prone to do the interpolation twice, in
> steps (1) and (3).
>

OK, then can you come up with an alternative approach that still conserves
"contain" in the example I provided?

Cheers,
    -Shane


> ****
>
> ** **
>
> *From:* Shane Stephens [mailto:shans@google.com]
> *Sent:* Thursday, August 11, 2011 9:18 PM
> *To:* Brian Manthos
> *Cc:* Tab Atkins Jr.; www-style list
>
> *Subject:* Re: [css3-images] Order of color-stop fixup****
>
>  ** **
>
> ...****
>
> Interpolating container-sensitive properties is still possible, it just
> takes more work. I outlined how to do it in my previous email, but here it
> is again:****
>
> (1) store non-resolved start and end values as part of the interpolated
> result (e.g. [cover 30%, contain 70%] is the result of a 30% interpolation
> between a cover gradient and a contain gradient)****
>
> (2) resolve start and end values against current size of container****
>
> (3) interpolate resolved values****
>
> ...****
>
Received on Friday, 12 August 2011 11:55:08 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:43 GMT