Gecko uses "style structs" that each hold the computed values of a few
CSS properties, and shares them between elements in some cases.
I’m aware that every style struct must contain either only inherited
properties, or only reset (non-inherited properties). Other than that,
what’s the guiding principle to decide how many structs to have, and
which properties go where? Why not have every longhand property in its
own "struct", sharable separately? Is there something you’d like to
change in Gecko’s distribution, but don’t because making the change
would be too painful?
--
Simon Sapin
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
