- From: Alex Mogilevsky <alexmog@microsoft.com>
- Date: Sun, 30 Oct 2011 21:12:17 +0000
- To: Håkon Wium Lie <howcome@opera.com>
- CC: David Hyatt <hyatt@apple.com>, Vincent Hardy <vhardy@adobe.com>, "www-style@w3.org list" <www-style@w3.org>
± From: Håkon Wium Lie [mailto:howcome@opera.com] ± Sent: Sunday, October 23, 2011 4:46 PM ± ± Alex Mogilevsky wrote: ± ± > I am strongly in favor of not breaking regions. ± ± If so, what should implementations do when regions don't fit pages/screens? I thought about the issue of people actually using regions everywhere (eventually) and use them in content that is not meant to be paginated, but then that kind of content is printed -- then it is reasonable to expect that regions will break across pages, similarly to other content that is not meant to be printed but still prints (such as huge floats). So I agree is reasonable to expect regions to paginate if they are being printed (in paged media). I am not sure what new technical issues that will bring, we'll need implementations to understand it better. The issue of DOM still remains. DOM has one representation for one element, even if that's on multiple pages/columns/regions. It is still a problem for non-region elements, so it may be OK to simply clarify how DOM behaves for paginated region. I will not object to allowing regions to break across pages or other regions. --Alex
Received on Sunday, 30 October 2011 21:12:45 UTC