CSS WG Blog – Minutes Toronto F2F 2019-06-05 Part I: CSS Text; Writing Modes; CSS Inline

Minutes Toronto F2F 2019-06-05 Part I: CSS Text; Writing Modes; CSS Inline

By Dael Jackson July 6, 2019 (Permalink)
Categories: resolutions

Florian presented a proposal to add space expansion properties to CSS to address use cases for languages that do not usually use spaces, but occasionally still want them.
- This would function similar to a text-transform when interacting with justification and word spacing.
- There was a desire to have a separation in properties between when spaces should be expanded manually vs automatically since those were different use cases.
Resolved: Add zero-width-space-expansion to Text 4, plan to rename
Resolved: Add manual vs automatic space expansion property (name and values TBD) to Text 4
Resolved: Add a note to the spec about considering not hyphenating proper nouns, but no normative changes (Issue #3927: hyphens:auto should not hyphenate Capitalized words)
Issue #3745 (Add new CSS text-transform values for math) will be deferred to TPAC when accessibility experts can be a part of the conversation as well as spend time to see if it’s possible to decouple the style and the markup accessibility

Resolved: Propagate direction, and writing mode from the body to the root without affecting computed styles w/optional text-orientation (Issue #3066: Does vertical writing mode of an HTML body element cause an orthogonal flow?)

Discussion of issue #3749 (resolved value of line-height) didn’t lead to a resolution but several people had actions to move the topic forward:
- florian will take some of the edits removed from CSS2.1 during the clean up of that spec and will add them to the Inline L3 spec.
- emilio will experiment with having Gecko return normal and see if it causes web compat issues.

Last updated 2019-07-06 23:29:05