- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Aug 2023 23:43:05 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text-4] Don't provide a language parameter for word-boundary-detection`, and agreed to the following: * `RESOLVED: name it auto-phrase` * `RESOLVED: add a principle saying you should break within the phrase instead of overflowing` * `RESOLVED: If your phrase is too long you should break at a normal word boundry rather than overflow` <details><summary>The full IRC log of that discussion</summary> <florian> q+<br> <TabAtkins> I'm weakly towards "phrase" just to suggest what it's actually doing.<br> <dael_> chrishtr: My understanding is we're all in agreement but need a name<br> <TabAtkins> and that keyword sounds reasonable from a complexity standpoint<br> <dael_> chrishtr: Three suggested are what I mentioned<br> <astearns> ack florian<br> <dael_> chrishtr: Reason to choose auto-phrase is because it could fallback if there isn't platform support<br> <dael_> florian: I think auto alone would not be good<br> <astearns> ack fantasai<br> <dael_> florian: I think auto alone would be a bad value because it already has a normal. auto-phrase is reasonable. I think keep-phrase would also be okay. I could go either way between those<br> <dael_> fantasai: Interacts a bit with property name for the whitespace text transform something which automatically inserts spaces at these points. A keyword that can be in both makes sense which auto-phrase does that. auto is too generic and keep-phrase doesn't work forword boundry<br> <dael_> florian: agree<br> <dael_> astearns: arguments for anything else?<br> <dael_> astearns: Objections to naming it auto-phrase<br> <dael_> RESOLVED: name it auto-phrase<br> <dael_> fantasai: As people impl this, one consideration we need to make sure is when you turn this on you don't end up triggering overflow b/c the phrases. We'll want to avoid that, particularly if it's long or it's foreign and you can't understand. Normal should be to wrap at a boundry not overflow<br> <dael_> chrishtr: Makes sense<br> <dael_> astearns: Anything to resolve here?<br> <dael_> fantasai: Prop: If your phrase is too long you should break at a normal word boundry rather than overflow<br> <dael_> astearns: Comfortable with that?<br> <dael_> florian: Yes<br> <dael_> astearns: prop: add a principle saying you should break within the phrase instead of overflowing<br> <dael_> astearns: obj?<br> <dael_> RESOLVED: add a principle saying you should break within the phrase instead of overflowing<br> <fantasai> s/within the phrase/at normal word boundary/<br> <dael_> RESOLVED: If your phrase is too long you should break at a normal word boundry rather than overflow<br> <fantasai> cool<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7193#issuecomment-1663101848 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 August 2023 23:43:07 UTC