Re: [css-regions] Named Flows, Elements and Box Generation

On Monday 2013-10-21 17:39 -0700, Alan Stearns wrote:
> 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.

I think the underlying motivation for [5] includes (at least) that:

 (a) the use of regions encourages creation of extra markup for
 stylistic purposes only, which is inconsistent with separation of
 content and presentation

 (b) the model of creating elements to be regions is inconsistent
 with the typical model of writing CSS where new property
 declarations cause observable changes, without requiring a
 complicated set of declarations and content changes to achieve an
 effect

I don't see how the above addresses these problems.

-David

> [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

-- 
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                          https://www.mozilla.org/   𝄂
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)