- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2022 17:10:25 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-ruby-1] Should auto-hide match use NFKC and/or strip white space?`, and agreed to the following: * `RESOLVED: only perform whitespace stripping before comparing the base and annotation texts` <details><summary>The full IRC log of that discussion</summary> <fremy> fantasai: we have a feature in ruby where if the annotated text and the base are identical if they are presented on top of each other<br> <fremy> fantasai: but if they are side by side, they are kept for example<br> <fremy> fantasai: the question is "what is identical"?<br> <fremy> fantasai: should we normalize before doing this?<br> <fremy> fantasai: should we deal with white space<br> <fremy> fantasai: should we collapse unicode characters that merge in rendering if possible? (NFKC)<br> <fremy> fantasai: but the internationalization group thought it might be too aggressive in some cases<br> <fremy> fantasai: they recommended NFC instead<br> <TabAtkins> q+<br> <fremy> fantasai: which only deal with things that are simpler (e.g. A + an accent vs A accent)<br> <florian> q+<br> <fremy> fantasai: so, do we want to perform NFC before comparing the texts?<br> <astearns> ack TabAtkins<br> <fremy> TabAtkins: I support whitespace stripping<br> <fremy> TabAtkins: because it can be due to source code formatting<br> <fremy> TabAtkins: but I don't think we should do NFC because we don't do this elsewhere<br> <fremy> TabAtkins: I expect that authors use the same typing convention in the same markup<br> <fremy> TabAtkins: we are not comparing html vs css<br> <astearns> ack florian<br> <fremy> florian: I agree about whitespace<br> <fremy> florian: for normalization, I'm less sure<br> <fremy> florian: if one persons types the text, and another the annotations<br> <fremy> florian: NFC is not very aggressive, I think it would make things more rational for users<br> <fremy> florian: however, it will be rare I think<br> <fremy> florian: but if it did occur, I think the correct behavior is to normalize<br> <fremy> florian: (so, preference for NFC, but not strong)<br> <jfkthame> +1 to nfc<br> <fremy> astearns: can we resolve on stripping whitespace, and leave off normalization?<br> <heycam> q+<br> <fremy> fantasai: I think yes, I agree with TabAtkins, we don't do it elsewhere<br> <fremy> fantasai: so it seems ok to drop this<br> <astearns> ack heycam<br> <fremy> heycam: this is just a content check, correct?<br> <fremy> heycam: we don't look at display:none etc... ?<br> <fremy> fantasai: we might be looking at display:none?<br> <fantasai> s/TabAtkins, we don't do it elsewhere/TabAtkins and Florian: it's definitely the right thing to do, but it's also not done elsewhere in the platform and is quite rare to mismatch/<br> <fremy> florian: but not generated content etc<br> <astearns> jfkthame: would you be OK not doing NFC, or would you prefer we resolve to use NFC?<br> <fremy> heycam: okay, hopefully the spec is very clear on that<br> <fremy> astearns: reading IRC comments<br> <fantasai> [note: those of us on the call are somewhat ambivalent about NFC, given pros and cons]<br> <jfkthame> astearns: I'd be ok with not, though I think it's less good (sorry, in another meeting)<br> <heycam> (I kind of don't quite understand the need for this automatic hiding, and why the author doesn't use visibility:hidden on ruby text that they know is the same as the base text)<br> <fremy> astearns: okay, since we have lots of doubts on NFC, let's just do whitespace and leave if at that<br> <fantasai> heycam, it's because whether it should be invisible or not depends on how it's styled<br> <fremy> florian: and also put an action on me to clarify the display:none behavior<br> <fantasai> heycam, and there's no selector for "this is the same text as the other thing" :)<br> <heycam> ok<br> <fantasai> heycam, plus it's what you want by default so we should do it by default<br> <fremy> astearns: so, the proposed resolution would be to only perform whitespace stripping before comparing the base and annotation texts<br> <fremy> astearns: any objection?<br> <fremy> RESOLVED: only perform whitespace stripping before comparing the base and annotation texts<br> <heycam> text-transform? :o<br> <fantasai> ”The content comparison for auto-hiding takes place prior to white space collapsing (white-space) and text transformation (text-transform) and ignores elements (considers only the textContent of the boxes).<br> <fremy> ACTION florian: make sure the way to determine what text we are talking about (display:none, etc...)<br> <fantasai> ”<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5995#issuecomment-1332483040 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 November 2022 17:10:27 UTC