- From: Mihai Balan <mibalan@adobe.com>
- Date: Wed, 5 Feb 2014 12:49:32 +0000
- To: Mihai Maerean <mmaerean@adobe.com>, "www-style@w3.org" <www-style@w3.org>
Isn't this actually covered by the new "Parallel flows" section in the fragmentation spec[1]? If anything, the fragmentation spec might add some wording to clarify the definition of a Block Formatting Context to refer to a block that contains all the floated boxes that are inside it, including fragment (boxes) of floats. Thoughts? [1] http://dev.w3.org/csswg/css-break/#parallel-flows Mihai Balan | Quality Engineer @ Web Engine team | mibalan@adobe.com | +4-031.413.3653 / x83653 | Adobe Systems Romania On 1/22/14 4:49 PM, "Mihai Maerean" <mmaerean@adobe.com> wrote: >Hi > >A block formatting context contains everything inside of the element >creating it. [1] > > >In the case of fragmentation contexts that create a Block Formatting >Context (BFC), there may be floats inside the fragmented content that also >have content inside them (which may have forced breaks). > >Consider this content (with css regions, which create BFCs by default): ><style> > .float { > float: left; > } > .break { > break-after: always; > } > .content { > flow-into: flow; > } > .region { > flow-from: flow; > } ></style> ><body> > <div class="content"> > <p>text</p> > <div class="float"> > <p>text</p> > <p class="break">text</p> > <p>text</p> > </div> > <p>text</p> > </div> > > <div class="region"></div> > <div class="region"></div> ></body> > > >Should the 3rd paragraph that's inside the float (the one after the forced >break) be laid out in the 2nd fragment container (region)? >If the forced break that's inside the float is being honoured, then does >that mean that the BFC of the 1st fragment container is being violated? > > >The answer to this question should be included in the css3-break spec. > > >regards, >Mihai Maerean > >[1] >https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_co >n >text > >[2] http://dev.w3.org/csswg/css-break/ > >[3] http://dev.w3.org/csswg/css-regions/ > >
Received on Wednesday, 5 February 2014 12:50:06 UTC