-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-text] Is the test CSS2/text/text-align-white-space-007.xht valid? #6344
Comments
I suspect the reason for this test is not just the end-of-line hanging, but mainly that the spec says:
The test does have the "may" piece of meta data, meaning that it's ok to fail, but given that this is merely an allowance for legacy behavior, rather than a requirement or event a suggestion, I agree just deleting the test is probably best. From a spec point of view, this used to be a requirement in css2, which css-text-3 merely relaxed, but if Firefox aligns with others, then we'll have interoperability on the opposite behavior, so maybe we should spec that behavior, even if it's a breaking change with CSS2. cc: @fantasai |
I think the reason the allowance was made to not justify pre-wrap text was because handling tabs seemed tricky while justifying text. I think the spec is fine, but removing the testcase so that we don't encourage implementations to pass it, sounds good to me. |
Having an automated test for this encourages implementations to align, but the spec isn't calling for this behavior, merely allowing as a less desirable but acceptable behavior. No need to draw attention to it. w3c/csswg-drafts#6344
Having an automated test for this encourages implementations to align, but the spec isn't calling for this behavior, merely allowing as a less desirable but acceptable behavior. No need to draw attention to it. w3c/csswg-drafts#6344
… recommended, a=testonly Automatic update from web-platform-tests Remove test for behavior allowed but not recommended Having an automated test for this encourages implementations to align, but the spec isn't calling for this behavior, merely allowing as a less desirable but acceptable behavior. No need to draw attention to it. w3c/csswg-drafts#6344 -- wpt-commits: d433691eff237c238fe0ff32d150279acfbac1d7 wpt-pr: 33709
… recommended, a=testonly Automatic update from web-platform-tests Remove test for behavior allowed but not recommended Having an automated test for this encourages implementations to align, but the spec isn't calling for this behavior, merely allowing as a less desirable but acceptable behavior. No need to draw attention to it. w3c/csswg-drafts#6344 -- wpt-commits: d433691eff237c238fe0ff32d150279acfbac1d7 wpt-pr: 33709
The test at CSS2/text/text-align-white-space-007.xht involves
white-space: pre-wrap
together withtext-align: justify
anddirection: rtl
.According to wpt.fyi, 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 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 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 separatebreak-spaces
value, which wraps similarly but preserves all spaces; for that value, the "expected" result would be correct, but forpre-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.The text was updated successfully, but these errors were encountered: