- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Sep 2018 00:53:48 +0000
- To: public-css-archive@w3.org
Patch (which could maybe use some wordsmithing): ```diff diff --git a/css-break-3/Overview.bs b/css-break-3/Overview.bs index f3cab08..a7748ed 100644 --- a/css-break-3/Overview.bs +++ b/css-break-3/Overview.bs @@ -1036,10 +1036,19 @@ Fragmented Borders and Backgrounds: the 'box-decoration-break' property</h3> on the left, the value ''slice'', on the right the value ''clone''. </div> - <p>UAs may also apply 'box-decoration-break' to control rendering - at bidi-imposed breaks, i.e. when bidi reordering causes an inline - to split into non-contiguous fragments. Otherwise such breaks are - always handled as ''slice''. + <p>UAs may also apply 'box-decoration-break' + to control rendering at bidi-imposed breaks-- + i.e. when bidi reordering causes an inline to split into non-contiguous fragments-- + and/or at display-type–imposed breaks-- + i.e. when a higher-level <a>display type</a> + (such as a <a>block-level box</a> / <a href="https://www.w3.org/TR/css-multicol-1/#spanning-columns">column spanner</a>) + splits an incompatible ancestor + (such as an <a>inline box</a> / <a>block container</a>). + Otherwise such breaks are always handled as ''slice''. + See [[css-writing-modes-3#bidi-algo|Applying the Bidirectional Reorderign Algorithm]] + in [[css-writing-modes-3#text-direction|CSS Writing Modes]], + <a href="https://www.w3.org/TR/CSS2/visuren.html#box-gen">CSS2§9.2 Block-level elements and block boxes</a>, + and <a href="https://www.w3.org/TR/css-multicol-1/#spanning-columns">CSS Multi-column Layout §6 Spanning Columns</a>. <p class=note> For inline elements, which side of a fragment is considered the broken edge ``` -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1706#issuecomment-420474809 using your GitHub account
Received on Wednesday, 12 September 2018 00:53:53 UTC