CSS WG Blog – Minutes Sydney F2F Part II – 2015-02-09 PM: Sizing, Text, Writing Modes, Multi-line/Block-Ellipsis

Minutes Sydney F2F Part II – 2015-02-09 PM: Sizing, Text, Writing Modes, Multi-line/Block-Ellipsis

By Dael Jackson March 25, 2015 (Permalink)
Categories: resolutions

Resolved: Add gregwhitworth as editor to Sizing
Resolved: Auto margins assumed to be zero for intrinsic size computation
The spec authors will work out a way to address the various ways percentages work.

Resolved: Treat replaced elements as ideographic chars for line-breaking. Based on data, possible add an exception for &nbsp.
It was agreed that the Text spec says that control characters should show, but everyone should coordinate when the change is made so that no one browser gets inundated with bug reports.
Resolved: Everyone will go coordinate on September being when control characters (Unicode class Cc) become visible. Implementations should aim to have it in their codebases by June, ready to go out in the next release after the coordination date.

Resolved: Keep sideways-left, mark as at-risk, possibly punt if it threatens CR-exit.
GregWhitworth will look at what options are valid for where writing-modes should propagate from – if it can be from body or if it has to come from root or if there are other approaches entirely.
Resolved: writing-mode: vertical-lr on the rt based on parent’s ‘display’ & ‘ruby-position’
Resolved: Drop the values if the SVGWG drops the values/properties, otherwise keep them.

Resolved: Replace region-fragment with ‘fragmentation’, written by Florian, determine where it belongs.
Resolved: Split fragmentation values of ‘overflow’ into a separate property. Further develop this in the overflow module.
Resolved: region-break gets folded into the new property, too.
Resolved: Florian added as editor to Overflow.

Last updated 2015-03-25 15:47:21