- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 May 2022 19:08:56 +0000
- To: public-css-archive@w3.org
> Chrome and Firefox make it invisible To clarify a bit: Chrome (if I understand correctly) just passes the codepoint through to the current font, so it may be invisible or render as tofu depending on the font in use. Firefox makes it invisible in Release/Beta versions, as the `layout.css.control-characters.visible` setting defaults to `false`, but renders it as a hexbox glyph in Nightly builds as the pref defaults to `true` there. (See https://searchfox.org/mozilla-central/rev/4274cdc16531e42b061d3091e0d146a62ff63b9b/modules/libpref/init/StaticPrefList.yaml#7516-7521.) I don't think there is any compelling reason to treat U+0000 any differently from other "spurious" control characters; they should all be rendered visible, as per CSS WG resolution. Depending on the current font (as Chrome currently does) is not a robust implementation approach. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7249#issuecomment-1119934680 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 May 2022 19:08:58 UTC