Closed
Bug 728911
Opened 13 years ago
Closed 13 years ago
Remove nsBlockFrame::mBullet and store it in a frame property instead (as needed)
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
RESOLVED
FIXED
mozilla13
People
(Reporter: MatsPalmgren_bugz, Assigned: MatsPalmgren_bugz)
References
Details
(Whiteboard: [inbound])
Attachments
(2 files)
4.74 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
33.73 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
This is mostly to support GetChildList() returning const nsFrameList&,
but I think it's a nice memory win as well since blocks only rarely
have a bullet.
Assignee | ||
Comment 1•13 years ago
|
||
Add a HasPushedFloat() method and move the PushedFloatProperty declaration to the .cpp file.
Attachment #598904 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 2•13 years ago
|
||
Remove the nsBlockFrame::mBullet member and store it in a frame property instead
(as needed). For an outside bullet, store it as a nsFrameList* to support
GetChildList(kBulletList). For an inside bullet, store it as frame pointer.
Use separate frame properties, mutually exclusive.
Attachment #598907 -
Flags: review?(bzbarsky)
![]() |
||
Comment 3•13 years ago
|
||
Comment on attachment 598904 [details] [diff] [review]
part 1, minor cleanup
r=me
Attachment #598904 -
Flags: review?(bzbarsky) → review+
![]() |
||
Comment 4•13 years ago
|
||
Comment on attachment 598907 [details] [diff] [review]
part 2, bullet properties
r=me
Attachment #598907 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 5•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/3f8c3a825d01
https://hg.mozilla.org/integration/mozilla-inbound/rev/b0f4734dba3c
Whiteboard: [inbound]
Target Milestone: --- → mozilla13
Comment 6•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/b0f4734dba3c
https://hg.mozilla.org/mozilla-central/rev/3f8c3a825d01
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•