CSS WG Blog – Minutes Sydney F2F 2016-02-01 Part II: Writing Modes, Line Grid, Overflow

Minutes Sydney F2F 2016-02-01 Part II: Writing Modes, Line Grid, Overflow

By Dael Jackson March 13, 2016 (Permalink)
Categories: resolutions

Koji shared that there are now over 900 test cases for Writing Modes, allowing a good sense of what properties don’t have two interoperable implementations.
- A document listing the properties where yellow items don’t have enough implementations is available here.
- Everyone praised the document and the work done in creating the test cases.
- With this feedback, Koji would like to target PR at TPAC.
sideways-* had a lot of failures, but still a lot of support for its need, so it will stay in the spec for now and drop to level 4 if it becomes the last blocker for REC.
Some of the failures for unicode-bidi are in the details of the embed behavior, which Unicode and the Web Platform are moving away from anyway. Those failures will be identified as failures in UAX9 implementation, not Writing Modes failures.
Several people received actions in order to continue progress on understanding these test results and getting more interoperable implementations.
Resolved: Make TCY fullwidth->proportional transform optional (text-combine-upright)

koji presented this proposal for a new line grid spec that is simplified in order to get more implementor interest.

The proposal changes the snapping to grid behavior to an attempt to control heights.
It also replaces line-grid with snap-height relying on css custom-properties to add more versatility.

Though everyone understood the goal of getting something implemented, there was a lot of concern that the proposal is too fragile to be useful, especially for vertical-rhythm.
Resolved: Make an ED for snap-sizing to work out details of proposal
Resolved: Editors koji and fantasai
Resolved: Add ideographic advance unit to Values and Units 4, come back to WG for approval after details worked out.

fantasai introduced her and TabAtkins’ work to trim down the overflow spec to just overflow-x and -y properties and to define ink and scrollable overflow.
Resolved: Hanging punctuation causes ink overflow. [Note: This discussion has since been reopened. See this email]
Resolved: clip-path and masking do not affect scrollable bounds
- esprehn will look into the compat for clip-path
Resolved: Spec the current behavior for nested transforms and add a note that this could be improved
Resolved: Drop border-box overflow concept (used for outlines); move it to UI 4 or Overflow 4
Discussed whether scrollable area should include margins on various elements. More testcases were wanted, and also author feedback.
A conversation about CSS containment and overflow:clip will be added to Tuesday’s agenda.

Last updated 2016-03-13 13:39:21