62894 - the rules in html.css could be moved to code to allow for faster style resolution and smaller footprint.

Status: RESOLVED WONTFIX

(Core :: CSS Parsing and Computation, defect, P3)

Description

[Marc Attinasi]

The rules in html.css are for internal use. We could conceivably move all of
those rules into code and speed up style resolution and reduce the memory
requirements of the style system (since the rules in html.css take up more than
50K).

Several ideas have been kicked around, from simply hard-coding the simple
selectors into the style contexts and/or html frames, to pre-processing the
html.css file into tables that drive the way that default values are initialized
in the style system.

There is much to investigate here...

Comment 1

[Hixie (not reading bugmail)]

From an ease-of-maintenance point of view, preprocessing the files would be
considerably nicer than hard-coding it. One of the best things about N6 is that
the ua.css file is a real CSS file! :-)

Comment 2

[Hixie (not reading bugmail)]

Netscape's standard compliance QA team reorganised itself once again, so taking 
remaining non-tables style bugs. Sorry about the spam. I tried to get this done 
directly at the database level, but apparently that is "not easy because of the 
shadow db", "plus it screws up the audit trail", so no can do...

Comment 3

[Marc Attinasi]

Moving to future for now...

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Taking those of attinasi's style system bugs that are really style system bugs
and still look valid.

Comment 5

[Boris Zbarsky [:bzbarsky]]

The footprint cost should be remeasured once bug 125246

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I don't think this is a problem given that (a) for memory use I believe we clone the UA sheet and (b) the rule hash is about as efficient as C++ code would be.

->wontfix