CSS WG Blog – Minutes Sophia-Antipolis F2F Part II 2014-09-08: z-index and SVG, Prioritizing image(color), randomize(), Animation and calc() of Keywords, Motion Path, Issues in Media Queries 4

Minutes Sophia-Antipolis F2F Part II 2014-09-08: z-index and SVG, Prioritizing image(color), randomize(), Animation and calc() of Keywords, Motion Path, Issues in Media Queries 4

By Dael Jackson October 15, 2014 (Permalink)
Categories: resolutions

Resolved: The root SVG element automatically creates a stacking context, as does foreignObject
Resolved: SVG elements honor z-index automatically (like flex items), without requiring position

There is generally high interest in animating to/from keyword values, but that means the keywords must be acceptable within calc(), which presents behavioral complications for many keywords.
Krit will investigate implementer interest and draft up a preliminary whitelist of keywords that could be included in calc().
The question of why calc() doesn’t have min/max functions was re-answered.

Krit presented his proposed solution for motion path which contains three long-hand properties; motion-path, motion-position and motion-rotation and their shorthand, motion.
The group received the proposal positively, but had several potential issues that will need to be addressed. They included:
- Calculating angle based on position
- Property name confusion
- Having to define motion-path multiple times
- Interaction between transforms and motion
Resolved: Make this an official editors draft with krit, shane, and TabAtkins as editors
The entire group was given an action to read, review, send comments about what you would like changed or noted or marked as an issue for FPWD

Resolved: No change: aspect ratios remain integers
Resolved: Deprecate device-* media features. Keep behavior, but authors “must not use”
Resolved: resolution MQ uses the vertical resolution when pixels are not square.
There was significant debate on the best way to handle high-contrast and color-inverted styling with several different approaches raised and discussed to maximize usability, but also encourage a11y-friendly code.
Resolved: Add color-inverted media feature with values none and inverted
Resolved: We will add one or more high-contrast related media features
Resolved: We won’t distinguish between “UA doesn’t support scripting” and “scripting is supported but turned off”
Resolved: Close issue 12 wrt View Mode spec as no change