- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Feb 2022 17:53:16 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `NULL must be visible for web-compat`. <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: NULL must be visible for web-compat<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/pull/6983<br> <TabAtkins> florian: It's simple. Currently specs require every control character to be made visible. It turns out it's not web-compatible to make NULL visible. He requests we add this to the list of characters that can be invisible.<br> <TabAtkins> florian: Chrome and Firefox currently do that anyway.<br> <PeterC> What's the spec text that this proposal would impact?<br> <TabAtkins> florian: So to the extent that's true, I'd agree.<br> <TabAtkins> jfkthame_: I'd lik to see content that was affected; there doesn't appear to be examples in the webkit bug<br> <TabAtkins> smfr: Looks like it affected iCloud Notes<br> <TabAtkins> smfr: Not sure why a null character got in there<br> <TabAtkins> jfkthame_: It's not something we've discussed in Firefox, but I'd personally entertain making it visible in FF.<br> <TabAtkins> jfkthame_: Wonder if apply can't just fix iCloud if there's a problem there<br> <TabAtkins> jfkthame_: stray control characters in content are generally a bad thing; even worse if people can't tell they're there<br> <TabAtkins> astearns: That's why we had the resolution to make things visible<br> <TabAtkins> astearns: Has FF tried to make the other control characters visible?<br> <TabAtkins> jfkthame_: My recollection is we do at least on prerelease channels; unsure if we've turned it on in release. Think we've had trouble getting other browsers to line up.<br> <TabAtkins> astearns: Anyone from Blink have comments?<br> <TabAtkins> iank_: Will have to check with koji.<br> <TabAtkins> florian: I think there was a point in Blink where they were visible if there was a character in the font for them.<br> <florian> s/a character/a visible glyph/<br> <TabAtkins> astearns: I suggest we loop in koji or whoever else in Blink; jfkthame_ please check the state of the visible-chars code in Firefox; we'll see if there are any other compat concerns besides iCloud notes.<br> <TabAtkins> astearns: And we'll come back to this on a later call.<br> <florian> s/for them./for them, but as that's generally not the case, they were still invisible. Not sure if that got fixed./<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6983#issuecomment-1049051081 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 February 2022 17:53:19 UTC