- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Feb 2022 13:00:54 +0000
- To: public-css-archive@w3.org
> Blink renders all characters in the DOM since [crbug.com/530342](https://crbug.com/530342). Note that (if I'm understanding correctly) Blink simply passes the control characters through the same rendering pipeline as printable characters, so the result may be visible or not depending on the particular font being used. Some fonts map control-character codepoints to invisible glyphs, and in this case they'll remain invisible in Blink, while other fonts may render a `.notdef` box or even some other graphical representation. This is not consistent with the [CSS Text requirement](https://drafts.csswg.org/css-text-3/#white-space-processing), which says: > Control characters ([Unicode category](https://drafts.csswg.org/css-text-3/#unicode-general-category) Cc)—other than tabs (U+0009), line feeds (U+000A), carriage returns (U+000D) and sequences that form a [segment break](https://drafts.csswg.org/css-text-3/#segment-break)—must be rendered as a visible glyph which the UA must synthesize if the glyphs found in the font are not visible -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6983#issuecomment-1050832986 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 25 February 2022 13:00:56 UTC