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

Re: [css3-images] Referencing <svg> element directly with element()

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 24 Feb 2012 13:17:21 -0500
Message-ID: <4F47D431.1020104@mit.edu>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-style@w3.org
On 2/24/12 1:07 PM, Boris Zbarsky wrote:
> On 2/24/12 1:02 PM, Tab Atkins Jr. wrote:
>> This is fine, actually. Even if the property that caused it to be not
>> rendered is inherited (and switching off the inheritance would return
>> it to being rendered), it's already in the "draw as a paint source"
>> clause. As a paint source, it uses its intrinsic appearance, which is
>> completely unaffected by layout.
> This is an incredibly huge pain to implement in the face of dynamic
> chages, because to do dynamic changes properly you need a useful concept
> of the "old style", and you're completely breaking that because the "old
> style" suddenly has circular dependencies on itself.

And more generally, this is yet another example of people thinking of 
"the rendering" as proceeding procedurally when it just doesn't.  You 
can't define that the styles suddenly behave completely differently 
based on what the styles were "in the past".  There is no "past".  You 
have to define the state of things, period, and how states of some 
things depend on states of other things, but with no implied timeflow in 
the process....

Received on Friday, 24 February 2012 18:17:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:12 UTC