CSS WG Blog – Minutes Seoul F2F Part I: 2014-05-19 AM- Flexbox, Transitions and Animations, calc(), Image Values 3

Minutes Seoul F2F Part I: 2014-05-19 AM- Flexbox, Transitions and Animations, calc(), Image Values 3

By Dael Jackson June 17, 2014 (Permalink)
Categories: resolutions

Resolved: Close issue on whether flex-basis: auto should resolve at computed value time. Clarify that the flex-basis: auto flips to width/height at used value time.
The flex resolution algorithm has been redrafted since the LCWD to be closer to the structure of the earlier CR draft while preserving the changes to handle flex values continuously approaching zero. (Various technical errors reported in the LCWD have also been fixed.) The editors are requesting review from those interested.
Some concerns about handling the static positions of absolutely-positioned child of were discussed:
- The group basically agreed to switch the flexbox/grid static position model to match a 0x0 static position placeholder box, but then also define that, depending on the alignment properties, the abspos child aligns relative to its static position differently.
- This should give the same layout results as what’s in the spec right now.
- A final resolution was held off until a decision could be made if the start point should be a box or a point.

For transitions, dbaron stated that there was only one major issue to be addressed before last call: how to handle when a transition starts/stops
- This is a major issue, however, and will require a dedication of time.
- Current hope is to be able to address it in June
For animations, dbaron stated that there was a lack of editorial resources to allow the spec to progress. Several people were suggested as being worth approaching for editorial help.
Shane discussed his work creating a cohesive approach to transitions, animations, and web animations which he intends to be the foundation of transitions/animations 4.
Resolved: Migrate Shane’s document (http://rawgit.com/shans/98cb810920ac43876020/raw/b77db7529411066c9f3cdd36a52d0b98553525f9/Overview.html) into the dev pages and the SotD section should say that it’s intended to be incorporated into Transitions and Animations 4.

The issue of whitespace in calc() was addressed.
The group agreed that there was no way to completely eliminate whitespace requirements, instead only being able to limit the instances of required whitespace. This lead the conversation toward what was easier for authors – getting close to the ideal of no whitespace or sticking with existing easy to remember, though non-ideal, whitespace rules.
Resolved: No change to calc() whitespace rules

The two disparate types of image fallback were addressed with the group expressing strong support for fallback to a color, but wishing to simplify image fallback.
Resolved: Drop fallback from image except fallback to color. Later we introduce that fallback as an explicit function.
Resolved: Cut out everything not defined for image-orientation, remove additions, move it to an appendix, call it obsolete and make a custom CR exit criteria stating it doesn’t need to be tested to exit CR.
Resolved: Specs that define obsolete features don’t need to test those features to exit CR.
Of the possible solutions for non-square pixels, the group leaned toward deferring to HTML’s handling of video.
TabAtkins plans on bringing requesting a LC for Image Values 3 on the first telecon after the meeting.

Last updated 2014-06-17 22:39:31