- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 May 2022 16:50:50 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `U+0000 invisible?`, and agreed to the following: * `RESOLVED: No change` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: U+0000 invisible?<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/7249<br> <TabAtkins> fantasai: Do we have Myles and jfkthame on the call?<br> <TabAtkins> astearns: Have jfkthame, not Mayles<br> <TabAtkins> smfr: Can probably speak for Myles<br> <TabAtkins> astearns: So we had previous resolution to amke all the CC characters visible<br> <TabAtkins> smfr: We had an issue on one Apple website, the text had U+0000 bytes in it<br> <TabAtkins> smfr: I'm guessing it's not *that* uncommon to have 0 bytes by mistake, due to server bugs? But we'd probably be okay with no change.<br> <TabAtkins> astearns: So you're suggesting close no change, and continue to specify they're displayed?<br> <TabAtkins> smfr: Think that's okay unless we have evidence the problem is more widespread.<br> <TabAtkins> emilio: I don't recall seeing issues with this in Nightly/Beta and we've had it for a long time<br> <TabAtkins> jfkthame: Also think we should ship it. Do occasionally see characters show up in Nightly that are invisible elsewhere, but it's rare.<br> <TabAtkins> jfkthame: And in all cases the users are better served by sites fixing their broken data<br> <TabAtkins> fantasai: We'd previously discussed doing a coordinated ship of this behavior - that was years ago, guess this didn't happen?<br> <TabAtkins> florian: Think we prepped coord but didn't pull the trigger.<br> <TabAtkins> florian: Firefox impl'd, Chrome impl'd partially (but leaves it to the font to render), Safari didn't impl.<br> <TabAtkins> astearns: But I think we can agree to resolve on this issue.<br> <TabAtkins> astearns: Any objections to no change on rendering of U+0000?<br> <TabAtkins> RESOLVED: No change<br> <TabAtkins> astearns: What can we do to coordinate making this part of the spec interoperable?<br> <TabAtkins> jfkthame: Think we need Blink to fix impl to not depend on the font's rendering.<br> <TabAtkins> astearns: Do we know if there's a blink issue?<br> <TabAtkins> jfkthame: There is, don't have it offhand<br> <fantasai> Maybe send that issue link to chrishtr and he can coordinate?<br> <TabAtkins> astearns: Suggest we find the issue number and post it here, see if we can get a response from Blink engineers<br> <TabAtkins> Yes, chrishtr is the right contact for coordinating this<br> <TabAtkins> smfr: We might be in a similar situation to Blink where it depends on the font, not sure<br> <TabAtkins> smfr: But this seems rare eough that I don't think coordinating shipping is necessary, seems hard to do for us in WebKit anyway<br> <TabAtkins> fantasai: I think we should open a separat eissue for the coordination<br> <TabAtkins> astearns: So we can close this issue witht he resolution we got, and continue coordination discussion later on.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7249#issuecomment-1137545872 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 May 2022 16:50:51 UTC