Closed Bug 75561 Opened 25 years ago Closed 25 years ago

AttributeAffectsStyle should be educated about HTML stylistic attributes so it can do its magic on HTML elements too

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 68198

People

(Reporter: attinasi, Assigned: attinasi)

References

Details

(Keywords: perf)

AttributeAffectsStyle currently cannot apply to HTML elements because of the implicit mapping of many HTML attributes to style properties. This makes it impossible to rely on the occurrance of a style rule with a given attribute selector for determining if the attribute will actually affect style. If we simply mapped the HTML stylistic attributes, possibly by element type, then we could probably get a big improvement in cases where non-stylistic attributes are changed and we end up reresolving style anyway. There is a bit of analysis to do here, like, where is the best place to do this? Currently, each HTML element is responsible for mapping their attributes to style properties, so they probably know best which ones are stylistic and which are not. Then again, a simple table of stylistic attributes could do the trick too... Some discussion of this has occurred on bug 68821.
*** Bug 75562 has been marked as a duplicate of this bug. ***
Crap is this a dup of bug 68198?
Looks like this bug is indeed covered by bug 68198, although that one looks at wider issues? Your call. Keywording anyway.
Keywords: mozilla0.9.1, perf
Typo in summary - fixing. Meditating on whether or not to dup this...
Summary: AttributeAffectsStyle should be educated about HTML stylistic attributes so it can do its magin on HTML elements too → AttributeAffectsStyle should be educated about HTML stylistic attributes so it can do its magic on HTML elements too
dup...
Strange, I just heard some quiet voices urging me to dup it, so I am compelled to do it. Sorry for the spamage. *** This bug has been marked as a duplicate of 68198 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
rsVERIFIED DUPLICATE since reporter resolved it
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.