Open
Bug 418964
Opened 16 years ago
Updated 2 years ago
Separate nsContainerFrame and nsSplittableFrame
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
NEW
People
(Reporter: jwatt, Unassigned)
Details
(Keywords: memory-footprint)
Spinning this off from bug 409565 as requested by bz. Currently SVG frames inherit nsSplittableFrame by virtue of inheriting nsContainerFrame. SVG frames are (currently?) not splittable, so they could save some space by if they didn't have to inherit nsSplittableFrame. Probably also other frames would benefit, e.g. nsHTMLImageFrame?
|
||
Comment 1•16 years ago
|
||
nsHTMLImageFrame is splittable. So it in fact inherits from nsSplittableFrame but not from nsContainerFrame (since it's not a container). The frames that would benefit from this are the non-splittable containers; outside of SVG this might be the form controls.
Keywords: footprint
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•