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

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

From: Brian Manthos <brianman@microsoft.com>
Date: Fri, 12 Aug 2011 12:05:02 +0000
To: Shane Stephens <shans@google.com>
CC: Tab Atkins Jr. <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <9710FCC2E88860489239BE0308AC5D1711CE5D@TK5EX14MBXC264.redmond.corp.microsoft.com>
Interpolate after knowing container size information rather than before...

-Brian

From: Shane Stephens [mailto:shans@google.com]
Sent: Friday, August 12, 2011 4:55 AM
To: Brian Manthos
Cc: Tab Atkins Jr.; www-style list
Subject: Re: [css3-images] Order of color-stop fixup


On Thu, Aug 11, 2011 at 10:46 PM, Brian Manthos <brianman@microsoft.com<mailto: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<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 12:05:33 GMT

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