- From: Shinyu Murakami via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Aug 2019 11:14:13 +0000
- To: public-css-archive@w3.org
> ISSUE 24 Whether this value should also be part of the UA defaults for Web content is currently under discussion. I strongly believe this value should be part of the defaults regardless of Web or ebooks, and the `normal` definition should be `space-first allow-end trim-adjacent`. I think that the current `normal` definition with `space-start` is the worst choice between `[trim-start | space-start | space-first]` because full-width opening punctuation at start of a line that does not begin the paragraph visually looks like beginning of a paragraph with indent because of the half em space that the full-width opening punctuation glyph has, and it makes bad readability. The remaining options are `trim-start` and `space-first`. I don't believe we can select `trim-start` as default because of web compatibility; it affects existing web contents that use intentionally full-width opening punctuation glyph at beginning of text blocks. So the only reasonable choice for default is `space-first`. Also, I strongly oppose changing defaults on the Web and ebooks. The difference between Web and ebooks is not obvious. For example, I am working on [Vivliostyle](https://vivliostyle.org/) that can be used as an ebook viewer and also can display/print Web contents with pagination; not obvious the Web content viewing with Vivliostyle is ebook content or not. This is important issue for us because [Support text-spacing](https://github.com/vivliostyle/vivliostyle.js/issues/182) is on our ToDo list. -- GitHub Notification of comment by MurakamiShinyu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2462#issuecomment-524820469 using your GitHub account
Received on Monday, 26 August 2019 11:14:15 UTC