- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Sep 2020 09:11:48 +0000
- To: public-css-archive@w3.org
Matching reality is good, so yes, we should change. But what is the behavior exactly? A tab character isn't a shift *by* a particular amount, it is a shit *to* a tab stop. I guess we just compute the potential tab stops independently for each preserved tab character? If so, the following sentence > Tab stops occur at points that are multiples of the tab size from the block’s starting content edge. just needs to be changed to > Tab stops occur at points that are multiples of the tab size from the starting content edge of the preserved tab's containing block’s. I think that's what browsers do. An alternative model where tab stops of different sizes somehow stack up seems complicated and unnecessary. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5489#issuecomment-685467990 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 September 2020 09:11:49 UTC