L. David Baron wrote:
Maybe we could somehow have one rule hash for every pseudo-element
for which we actually have rules? That could avoid getting too
bloated (since in many cases there are no pseudo-element rules).
We could do that, but we'd have more rule hashes than one might think in
the UA level due to all the anon boxes that we treat as pseudo-elements
(most of which we do have rules for in ua.css). We'd also have a rule
hash per different made-up tree pseudo-element. It might be ok, though.
3) Perhaps combine the rule processor data for the "main" style
resolution and the pseudo-probing, since the latter just uses the same
data with the additional pseudo-tag tossed in.
Makes sense if it's easy; I haven't looked at how much code it would
require changing.
Yeah, I haven't either. The relevant frame constructor code is in
enough flux in my tree right now that I didn't really want to experiment
against it until things stabilize.
I'll look into at least doing items 2 and 3.
-Boris
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
