Re: getComputedStyle / getOverrideStyle

> Yes, but in this case, animations setting animated properties into
> getOverrideStyle (as specified in the SVG spec), it's the UA itself that
> does that, and the UA of course also has write-permission into
> getComputedStyle

"the UA" is not a monolithic entity... for example, most of Mozilla code cannot
write into the computed style declaration.

> I'm trying to implement it in my LXViewer, and that's why I need to know how
> it works. Are you saying that writing into getOverrideStyle (by UA itself or
> a user), that also changes the values that are in getComputedStyle?


> If that's true, I can see how that works now, For a given element, the UA
> computes the computed properties based on stylesheets etc. and then looks at
> the override style on the element to see if there are any properties there,
> and then "overrides" the computed style with those.

Not quite.  The UA just computes based on stylesheets, period. The override
style is just another author sheet, one that has priority over other author
sheets (you can think of it as coming after all other author sheets).

In particular, user !important rules override the override style.

Economists state their GNP growth projections to the
nearest tenth of a percentage point to prove they have a
sense of humor.
                             -- Edgar R. Fiedler

Received on Thursday, 6 November 2003 15:18:47 UTC