Closed
Bug 176139
Opened 22 years ago
Closed 22 years ago
GetMappedAttributeImpact called during HTML parsing
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: dbaron, Assigned: dbaron)
Details
(Keywords: perf, Whiteboard: [whitebox])
As noted in bug 22820 comment 39, we're doing work to handle changes when we're
intiially constructing the page. This should be avoidable.
|
Assignee | |
Updated•22 years ago
|
|
||
Comment 1•22 years ago
|
||
A little extra background from talking about this with jst:
Currently we use the result from GetMappedAttributeImpact (during parsing) to
decide whether the attribute goes into mMapped or mUnmapped in nsHTMLAttributes.
There's no provision for changing an attribute from unmapped to mapped on the
fly. If we defer calling GetMappedAttributeImpact we'll need to have a way of
lazily calling it when the attribute value changes or the attribute is removed.
|
||
Updated•22 years ago
|
Whiteboard: [dev notes]
|
|
Assignee | |
Comment 2•22 years ago
|
||
OK, nevermind.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
|
|
||
Updated•22 years ago
|
Whiteboard: [dev notes] → [whitebox]
You need to log in
before you can comment on or make changes to this bug.
Description
•