[Bug 11144] Elastic region extents based on content


--- Comment #1 from G. Ken Holman <gkholman@cranesoftwrights.com> 2010-11-03 14:18:51 UTC ---
I recognize that dynamically changing the extent on a per page basis imposes
considerable difficulty and situations similar to "race conditions" when
dealing with retrieved markers changing the extent of the region.

If this is considered by the committee to be too onerous, then a compromise
position regarding this feature would be as follows:  disregarding retrieved
markers, the elasticity of the region is determined solely by the content of
the flow defined in the static content.  That calculated extent would then be
fixed for all pages in the page sequence, and any retrieved content requiring
more extent would be treated as overflow.

Though it would be nice if it were truly elastic on a per-page basis.


Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Received on Wednesday, 3 November 2010 14:18:53 UTC