- From: Alan Stearns <stearns@adobe.com>
- Date: Mon, 21 Oct 2013 17:39:01 -0700
- To: "www-style@w3.org" <www-style@w3.org>
Hey all, As I mentioned in last week's telecon, I've been posting about how named flows interact with overflow:fragments. An overflow:fragments element can be useful at the end of a region chain [1]. Adding a named flow to an overflow:fragments element enhances scriptability [2]. And named flows can be used to link overflow:fragments elements together [3]. All of this shows how overflow:fragments can be used as a box-generation mechanism for named flows. And each of these cases has at least one variant that does not add region elements to the markup. So I think this shows that the issue [4] on box generation for regions can be addressed with overflow:fragments and other box-generation mechanisms we define in the future (such as page template or grid template slots). The way that named flows and overflow:fragments interact is through applying flow-from to the overflow:fragments element itself. It *requires* that flow-from applies to elements. So I think this shows that the elements issue [5] should be closed as well. If anything, we need to restrict flow-from from applying to ::nth-fragment() pseudo-elements in the Overflow draft, in exactly the same way that the content property does not apply to these particular pseudo-elements. The flow-from property needs to apply to elements to interact properly with the rest of CSS. Thanks, Alan [1] http://lists.w3.org/Archives/Public/www-style/2013Oct/0239.html [2] http://lists.w3.org/Archives/Public/www-style/2013Oct/0250.html [3] http://lists.w3.org/Archives/Public/www-style/2013Oct/0266.html [4] https://www.w3.org/Bugs/Public/show_bug.cgi?id=15733 [5] https://www.w3.org/Bugs/Public/show_bug.cgi?id=16858
Received on Tuesday, 22 October 2013 00:39:21 UTC