Re: [css3-gcpm] Incompatibilities with css3-content

In this case it seems that the implementation cost of move-to is only at the
parser level (what I imagined originally)

Giovanni

2009/2/9 Boris Zbarsky <bzbarsky@mit.edu>

> Giovanni Campagna wrote:
>
>> How much memory does a new property need?
>>
>
> In a naive implementation, for each property, for each element you need to
> store the specified, computed, and used value.  An obvious optimization is
> to not store specified values for properties that are not actually
> specified, and to collapse computed and used values for all properties where
> the two do not differ (e.g. float would fall in this bucket).
>
> For this particular case, the value seems to be able to fit into an integer
> of some sort without too much trouble, so the answer would seem to be "a few
> bytes per node", modulo optimizations involving sharing style data across
> nodes.
>
> -Boris
>