- From: Javier Fernandez Garcia-Boente via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Dec 2020 17:57:20 +0000
- To: public-css-archive@w3.org
javifernandez has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-text] Inconsistency on how 'break-spaces' value handles the first space of an overflowing sequence == I think the following statement of the White Space Processing Phase II is incorrect, or at least, inconsistent with other statements about how we should handle the first space of an overflowing sequence when the white-space property is set to 'break-spaces': https://drafts.csswg.org/css-text-3/#white-space-phase-2 > If white-space is set to break-spaces, hanging or collapsing the advance width of the spaces, tabs, or other space separators at the end of the line is not allowed; those that overflow must wrap to the next line. I think the last sentence "those that overflow must wrap ..." is not correct and should clearly state "those after the first space that overflow ..." instead (or something like this). The current statement is inconsistent with what Phase I describes: https://drafts.csswg.org/css-text-3/#white-space-phase-2 > ... However, for pre-wrap, a soft wrap opportunity exists at the end of a sequence of spaces and/or tabs, while for break-spaces, a soft wrap opportunity exists after every space and every tab. It's even clearer in the specific prose of the 'break-spaces' value: https://drafts.csswg.org/css-text-3/#valdef-white-space-break-spaces > A line breaking opportunity exists after every preserved white space character and after every other space separator (including between adjacent spaces). Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5783 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 December 2020 17:57:22 UTC