- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Oct 2022 16:10:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `trim-end better than allow-end`, and agreed to the following: * `RESOLVED: Incorporate trim-end behavior into the normal keyword` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: trim-end better than allow-end<br> <TabAtkins> fantasai: about text-spacing<br> <TabAtkins> fantasai: ONe of its fucntions is to handle the blank hash(sp?) of CJK font spacing<br> <TabAtkins> fantasai: a couple of values of how to handle it at start or end of th eline, trim or not<br> <TabAtkins> fantasai: proposal from murakami-san is incorporate the trim-end behavior into the 'normal' value<br> <TabAtkins> fantasai: review from i18n is to recommend adopting this<br> <fantasai> https://www.w3.org/TR/css-text-4/#text-spacing-property<br> <fantasai> s/hash(sp?)/half/<br> <fantasai> s/CJK font spacing/CJK punctuation/<br> <TabAtkins> Rossen_: Objections?<br> <TabAtkins> [none]<br> <TabAtkins> RESOLVED: Incorporate trim-end behavior into the normal keyword<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7055#issuecomment-1276421476 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 October 2022 16:10:06 UTC