Closed
Bug 854
Opened 26 years ago
Closed 25 years ago
{sink} content sink needs to support nested incremental reflow
Categories
(Core :: DOM: Core & HTML, defect, P4)
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: angus, Assigned: vidur)
References
()
Details
This test case is a document with a <UL> followed by 500 <LI>s followed by a
</UL>.
If you load this URL in IE, you'll see that it lays out list items
incrementally.
We don't show anything until we hit the </UL> - you'll notice that the same set
of list items broken up into 25 UL groups renders much faster (see test case at:
http://www.mozilla.org/nglayout/testcases/stress/500in25uls.html )
We should lay out long lists incrementally. We'll need to do this in order to
support an Aurora Front End in HTML.
Summary: We aren't incrementally laying out large lists → content sink needs to support nested incremental reflow
Currently the content sink only allows the body to respond to incremental
(appended) reflow. This is a somewhat arbitrary limitation that needs repair.
Comment 4•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
It doesn't look like a DOM issue. QA contact re-assigned to Layout owner.
Summary: content sink needs to support nested incremental reflow → {inc} content sink needs to support nested incremental reflow
Updated•25 years ago
|
Assignee: peterl → vidur
Comment 9•25 years ago
|
||
This should fall out of the content sink cleanup work...
Assignee | ||
Updated•25 years ago
|
Summary: {inc} content sink needs to support nested incremental reflow → {sink} content sink needs to support nested incremental reflow
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•25 years ago
|
||
Fixed by content sink changes on 10/26/1999. Stress away, Angus!! :-)
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 11•25 years ago
|
||
Fixed in the Nov 15th build.
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•