- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 May 2019 16:17:57 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Hanging/collapsing fixed-width spaces`, and agreed to the following: * `RESOLVED: fixed width spaces U+2000 and up are treated like U+0020 and U+3000 -- hang / disappear at end of line` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Hanging/collapsing fixed-width spaces<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/3879<br> <fantasai> florian: Spaces ...<br> <fantasai> florian: Currently only U+0020 and U+3000 are able to hang<br> <fantasai> florian: But other fixed-width spaces don't<br> <fantasai> florian: don't know if there was a specific reason not to include them, or some kind of oversight<br> <fantasai> fantasai: I think we knew that nbsp couldn't hang<br> <fantasai> fantasai: so we only had U+0020 hang<br> <fantasai> fantasai: later on added ideographic space in response to feedback from Japan<br> <fantasai> fantasai: Didn't re-evaluate other fixed-width space<br> <fantasai> florian: Compat risk?<br> <fantasai> fantasai: Probably low, most people don't know they exist<br> <fantasai> fantasai: I'd be willing to change the spec and see how it goes<br> <fantasai> fantasai: We'll need to except nbsp<br> <fantasai> fantasai: also ogham space mark?<br> <fantasai> florian: There's about whether spaces can hang at the end of the line in pre-wrap<br> <fantasai> florian: separate question of whether they disappear when wrapping 'white-space: normal'<br> <fantasai> florian: Not sure how to deal with ogham<br> <fantasai> fantasai: will have to as i18n<br> <fantasai> RESOLVED: fixed width spaces U+2000 and up are treated like U+0020 and U+3000 -- hang / disappear at end of line<br> <fantasai> http://www.fileformat.info/info/unicode/category/Zs/list.htm<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3879#issuecomment-490552390 using your GitHub account
Received on Wednesday, 8 May 2019 16:17:58 UTC