Gecko:Continuation Model: Difference between revisions

Jump to navigation Jump to search
m
→‎Reflow statuses: - Update nsIFrame link to point to mozilla-central source.
m (→‎Reflow statuses: - Update nsIFrame link to point to mozilla-central source.)
Line 70: Line 70:
== Reflow statuses ==
== Reflow statuses ==


The aStatus argument of Reflow reflects that. NS_FRAME_COMPLETE means that we reflowed all the content and no more next-in-flows are needed. At that point there may still be next in flows, but the parent will delete them. NS_FRAME_NOT_COMPLETE means "some content did not fit in this frame". NS_FRAME_OVERFLOW_INCOMPLETE means that the frame is itself complete, but some of its content didn't fit: this triggers the creation of overflow containers for the frame's continuations.  NS_FRAME_NOT_COMPLETE and NS_FRAME_REFLOW_NEXTINFLOW means "some content did not fit in this frame AND it must be reflowed". These values are defined and documented in [http://lxr.mozilla.org/seamonkey/source/layout/generic/nsIFrame.h nsIFrame.h] (search for "Reflow status").
The aStatus argument of Reflow reflects that. NS_FRAME_COMPLETE means that we reflowed all the content and no more next-in-flows are needed. At that point there may still be next in flows, but the parent will delete them. NS_FRAME_NOT_COMPLETE means "some content did not fit in this frame". NS_FRAME_OVERFLOW_INCOMPLETE means that the frame is itself complete, but some of its content didn't fit: this triggers the creation of overflow containers for the frame's continuations.  NS_FRAME_NOT_COMPLETE and NS_FRAME_REFLOW_NEXTINFLOW means "some content did not fit in this frame AND it must be reflowed". These values are defined and documented in [http://mxr.mozilla.org/mozilla-central/source/layout/generic/nsIFrame.h nsIFrame.h] (search for "Reflow status").


== Dynamic Reflow Considerations ==
== Dynamic Reflow Considerations ==
Confirmed users
490

edits

Navigation menu