[css-text-4] Should no-compress be a value of text-space? · Issue #7079 · w3c/csswg-drafts · GitHub
Skip to content
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-4] Should no-compress be a value of text-space? #7079

Open
r12a opened this issue Feb 22, 2022 · 2 comments
Open

[css-text-4] Should no-compress be a value of text-space? #7079

r12a opened this issue Feb 22, 2022 · 2 comments
Labels
Commenter Response Pending css-text-4 i18n-clreq Chinese language enablement i18n-jlreq Japanese language enablement i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. Needs Author Feedback

Comments

@r12a
Copy link
Contributor

r12a commented Feb 22, 2022

10.2. Character Class Spacing: the text-spacing property

no-compress
Justification must not compress text-spacing. (If this value is not specified, the justification process may reduce autospacing except when the spacing is at the start or end of the line.)

Suppressing compression is an odd man out here, since it has to do with justification. I see justification as something that is applied to the text after the text-space adjustments have been applied (or not). Seems like it would be more intuitive to make no-compress an optional value for text-justify, rather than one for text-space.

@r12a r12a added the i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. label Feb 22, 2022
@xfq xfq added the css-text-4 label Feb 23, 2022
@fantasai
Copy link
Collaborator

@r12a The no-compress option here is specifically about the extra space added by text-spacing, and not about whether compression is allowed in general.

fantasai added a commit that referenced this issue Feb 21, 2023
* Remove non-useful keyword combinations #4246 #8288
* Split into longhands #4246 #7183 #8288
* Ensure off values for each thing #8288 #6950
* Add insert|replace to allow replacing incorrect space characters #318 #8263 #7183
* Make space-first the initial value #2462
* Allow hanging-punctuation to hang leading ideographic spaces #2462
* Move no-compress to text-justify #7079

See https://lists.w3.org/Archives/Public/www-style/2023Feb/0002.html
@fantasai
Copy link
Collaborator

Fixed in 2966104 by moving no-compress to text-justify.

However this opens up a couple questions:

  • If it's restricted to controlling the spacing managed by text-spacing and not spacing in general, should the keyword be renamed to something more specific? (To what, specifically?)
  • Alternatively, should no-compress shut off all justification compression?

It might be good to hear from JLTF &co what sort of control is desired here. I'll note that the inter-script autospace values introduced by CSS are fairly minimal (1/8em, to be conservative) so probably shouldn't be compressed much more than they are in any case.

@fantasai fantasai added i18n-jlreq Japanese language enablement i18n-clreq Chinese language enablement Commenter Response Pending Needs Author Feedback labels Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Commenter Response Pending css-text-4 i18n-clreq Chinese language enablement i18n-jlreq Japanese language enablement i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. Needs Author Feedback
Projects
None yet
Development

No branches or pull requests

3 participants