Re: [csswg-drafts] [css-text] Question re white space processing rules for U+000D (#855)

The CSS Working Group just discussed `Question re white space processing rules for U+000D\`, and agreed to the following:

* `RESOLVED: amend the previous resolution to include form feeds so they're processed same as lone CRs`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Question re white space processing rules for U+000D\<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/855#issuecomment-451191125<br>
&lt;dael> fantasai: We discussed handling lone carriage returns. Last couple resolution talked about carriage, but not form feeds. Current spec form feeds are different than every other control character. They are not rendered<br>
&lt;dael> fantasai: Wanted to know what we wanted to do. Treat as 0 width space or no?<br>
&lt;fantasai> https://www.w3.org/TR/css-text-3/#white-space-processing<br>
&lt;dael> fantasai: Spec section ^<br>
&lt;fantasai> Form feeds (U+000C) (that are not segment breaks) are rendered as a zero-width space (U+200B). Control characters (Unicode category Cc) other than tab (U+0009), line feed (U+000A), and form feed (U+000C), must be rendered as a visible glyph which the UA must synthethize if the glyphs found in the font are not visible and otherwise treated as any other character of the Other Symbols (So) general category and<br>
&lt;fantasai> Common script. The UA may use a glyph provided by a font specifically for the control character, substitute the glyphs provided for the corresponding symbol in the Control Pictures block, generate a visual representation of its code point value, or use some other method to provide an appropriate visible glyph. As required by [UNICODE], unsupported Default_ignorable characters must be ignored for rendering.<br>
&lt;dael> astearns: I don't have a strong opinion but makes sense to treat form feeds in a consistent way<br>
&lt;dael> astearns: Anyone have a reason to treat form feeds differently?<br>
&lt;dael> astearns: Obj to amend the previous resolution to include form feeds so they're processed same as lone CRs?<br>
&lt;dael> RESOLVED: amend the previous resolution to include form feeds so they're processed same as lone CRs<br>
&lt;dael> astearns: That will require test changes an that will get us feedback<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/855#issuecomment-456891189 using your GitHub account

Received on Wednesday, 23 January 2019 17:24:14 UTC