@@ -1886,15 +1886,28 @@ Line Breaking Details</h3>
18861886 i18n/css3-text-line-break-baspglwj-130.html
18871887 i18n/css3-text-line-break-baspglwj-131.html
18881888 </wpt>
1889- <li> UAs that allow wrapping at punctuation other than spaces should prioritize breakpoints.
1889+
1890+ <li> UAs that allow wrapping at punctuation
1891+ other than <a>word separators</a>
1892+ in writing systems that use them
1893+ <em> should</em> prioritize breakpoints.
18901894 (For example, if breaks after slashes are given a lower priority than spaces,
1891- the sequence "check /etc" will never break between the "/" and the "e".)
1892- As long as care is taken to avoid such awkward breaks, allowing breaks at
1893- appropriate punctuation other than spaces is recommended, as it results
1894- in more even-looking margins, particularly in narrow measures.
1895+ the sequence “check /etc” will never break between the "/" and the "e".)
1896+ As long as care is taken to avoid such awkward breaks,
1897+ allowing breaks at appropriate punctuation other than <a>word separators</a>
1898+ is recommended,
1899+ as it results in more even-looking margins, particularly in narrow measures.
18951900 The UA may use the width of the containing block, the text's language,
1901+ the 'line-break' value,
18961902 and other factors in assigning priorities:
18971903 CSS does not define prioritization of line breaking opportunities.
1904+ Prioritization of <a>word separators</a> is not expected,
1905+ however,
1906+ if ''word-break: break-all'' is specified
1907+ (since this value explicitly requests line breaking behavior
1908+ not based on breaking at <a>word separators</a> )--
1909+ and is forbidden under ''line-break: anywhere'' .
1910+
18981911 <li> Out-of-flow elements do not introduce a <a>forced line break</a>
18991912 or <a>soft wrap opportunity</a> in the flow.
19001913
0 commit comments