CSS WG Blog – Minutes TPAC F2F Nov. 2013 Part III: Box Generation and Elements as Regions; CSS Writing Modes, Tr Fallback; Charter; Styling Left vs. Right Pages; Filter Effects; CSS Transforms; Geometry API Spec; CSS3-Text; Background and Borders 3; Transitions; CSS Shapes; Background and Borders 4; Longhand for List Properties

Minutes TPAC F2F Nov. 2013 Part III: Box Generation and Elements as Regions; CSS Writing Modes, Tr Fallback; Charter; Styling Left vs. Right Pages; Filter Effects; CSS Transforms; Geometry API Spec; CSS3-Text; Background and Borders 3; Transitions; CSS Shapes; Background and Borders 4; Longhand for List Properties

By Dael Jackson November 23, 2013 (Permalink)
Categories: resolutions

Koji discussed the ongoing issue about how Tr should fallback, rotated or upright.
Another solution was also raised to leave the fallback behavior undefined or must not.
Resolved: Accepting option A, “If the vert alt glyph is not present in the font, UA may, but is not expected to, substitute the glyph,” with term “MAY WISH TO” and referencing RFC6919.
Resolved: Take CSS Writing Modes to Last Call.

Bert will update the list of deliverables on the charter.
Later the possibility of asynchronous decision making was discussed. The group briefly considered the benefits and problems of asynchronous decisions, but decided that it would be worth discussing further.
Dbaron will write up a proposal for asynchronous decision making.

Leaverou brought up the difficulties with writing/designing books in CSS and that no adequate solution had come from the mailing list.
A potential solution was to adapt Regions to address the problems, but it was decided that implementor experience was needed to decide how to handle the adaptation.
The group did decide that the fix did belong in Regions or Pages, depending on which was receiving priority.

The group discussed if SVGPoint.matrixTransform should be retained and it was decided to get a better sense of how much it’s used before making the remove/retain decision.
They also investigated ways of creating intersections between shapes.
A question was raised about if rect should be mutable or unmutable. Krit requested that this issue (and others) be raised on public-script-coord.

The changes to auto hyphenation were discussed, including when soft hyphens should be available.
Another issue discussed was one raised by DigiPub asking if text-align should become a shorthand for text-align-last. It was decided that fantasai will e-mail a summary of the issues for discussion at the next telecon.
Resolved: We won’t rename text-indent: each-line
The last issue was in regards to letter-spacing applying to grapheme clusters.

Fantasai reviewed the issues remaining after the edits to borders.
The topic of ensuring animating border-radius received a lot of discussion with the decision being made to create examples that show the possible solutions.
The lack of a definition for the order of shorthands was discussed.
A potential solution of referring to a propdef was raised, but where the information on how to read propdef should be placed was unclear with people disagreeing as to if it needed to be a rec track document or not.
Potentially removing three value positions and the implication for one value positions was discussed with the group leaning toward only allowing one value positions.
TabAtkins and fantasai will write up text for transform-origin to reduce/alter inconsistencies with background-position.

Potential names for what’s being called border-clip and border-corner-shape were discussed.
Interest was expressed in the ability to have multiple borders.
Fantasai will write up a proposal.