- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Jun 2021 09:55:07 +0000
- To: public-css-archive@w3.org
jfkthame has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-text] Is the test CSS2/text/text-align-white-space-007.xht valid? == The test at CSS2/text/text-align-white-space-007.xht involves `white-space: pre-wrap` together with `text-align: justify` and `direction: rtl`. According to [wpt.fyi](https://wpt.fyi/results/css/CSS2/text?label=master&label=experimental&aligned&q=text-align-white-space-007.xht), it currently passes on Firefox but not on Safari, Edge or Chrome. However, I'm finding it difficult to understand why the expected behavior would be "correct", and a [change I'd like to make in Gecko](https://bugzilla.mozilla.org/show_bug.cgi?id=1712703) will cause it to start "failing" there as well (while fixing other testcases). It looks to me like this testcase does not take account of the fact that the [`pre-wrap` value](https://drafts.csswg.org/css-text-3/#valdef-white-space-pre-wrap) allows line-end spaces to hang (as noted in the summary table of behaviors below the list of values). I guess it predates the introduction of the separate `break-spaces` value, which wraps similarly but preserves all spaces; for that value, the "expected" result would be correct, but for `pre-wrap` it seems wrong. If my understanding is correct that this testcase is invalid (at least according to current specs; it may have been valid when written), I would suggest we simply delete it. There are newer tests of these properties under the `/css/css-text/` directory. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6344 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 June 2021 09:56:11 UTC