- From: Shinyu Murakami via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Oct 2023 08:52:15 +0000
- To: public-css-archive@w3.org
> A new critical regression case for `space-first` was reported ([source](https://xtech.nikkei.com/atcl/nxt/news/18/16172/).) Updating the [table](https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1774991353). Here is the html code: ```html <p> （1）量販価格帯の新たなEVシリーズを2027年以降、北米を皮切りに投入予定<br> （2）コンパクトスポーツ多目的車（SUV）を含む、グローバルで人気の高いセグメントに向けたEVシリーズ<br> （3）両社で世界規模での生産を可能にする設計を検討<br> （4）次世代バッテリーに関する協業の深化についても検討 </p> ``` In my [`space-first` proposal](https://github.com/w3c/csswg-drafts/issues/2462), each line after `<br>` must be treated as a first line that "space-first" is applied. Now I found that the definition of `space-first` was changed between 2022-12-31 and 2023-03-01: - https://www.w3.org/TR/2022/WD-css-text-4-20221231/#valdef-text-spacing-space-first > Behaves as space-start on the first line the block container and each line after a forced line break but as trim-start on all other lines. - https://www.w3.org/TR/2023/WD-css-text-4-20230301/#valdef-text-spacing-trim-space-first > Set fullwidth opening punctuation with full-width glyphs (spaced) on the first line the block container. Otherwise as trim-auto (unless allow-end is also specified). I believe this is a mistake. -- GitHub Notification of comment by MurakamiShinyu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1780688084 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 October 2023 08:52:17 UTC