Closed
Bug 60378
Opened 24 years ago
Closed 3 years ago
unneeded style resolutions for list/select items.
Categories
(Core :: Layout: Form Controls, defect, P4)
Core
Layout: Form Controls
Tracking
()
RESOLVED
INCOMPLETE
Future
People
(Reporter: buster, Assigned: john)
Details
(Keywords: perf)
This needs verification, but I think we do a bunch of unnecessary style
resolution when we create frames for lists and combo boxes. The vast majority
of the time (and in the real world as it exists today, very close to 100% of the
time), items in lists have identical style. But we resolve style for each
individually, just in case. This seems very wasteful. There should be some way
we can detect that style for each is identical, and skip the resolution.
Subsequent items could just grab their style context from the first.
Alternately, could we shift the cost to the back end? Do the initial layout as
if they have identical style, then scan to verify, and if it isn't true fire off
a style changed reflow to the items that need it?
Since Rod is looking at doing lazy instantiation of list contents, it's critical
to make initial list layout very fast. We need some quantify numbers, but I'll
bet style resolution is a major performance cost.
Updated•24 years ago
|
Status: NEW → ASSIGNED
Updated•23 years ago
|
Priority: P2 → P4
Updated•23 years ago
|
QA Contact: vladimire → tpreston
Comment 3•22 years ago
|
||
Isn't roc / dbaron working on that?
Assignee | ||
Comment 5•22 years ago
|
||
This is a good time to do a select layout rewrite as well (one is sorely needed).
Status: NEW → ASSIGNED
Updated•22 years ago
|
Summary: unneeded style resolution → unneeded style resolutions for list/select items.
Updated•15 years ago
|
QA Contact: tpreston → layout.form-controls
Comment 6•3 years ago
|
||
Closing this as resolved:incomplete, there has been no activity on this issue in the last 19 years and the assignee has the account disabled as well. Please re-open it if this issue is still relevant today.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•