CSS WG Blog – Minutes Berlin F2F 2018-04-11 Part II: CSS Scoll Snap, CSS Text 3, Web Animations, CSS Fonts, CSS Text & Text Decoration, Ruby

Minutes Berlin F2F 2018-04-11 Part II: CSS Scoll Snap, CSS Text 3, Web Animations, CSS Fonts, CSS Text & Text Decoration, Ruby

By Dael Jackson June 9, 2018 (Permalink)
Categories: resolutions

The group agreed that the focus should be encouraging users to reference the new version of Scroll Snap and that writing a guide to what can be done in both old and new would not move toward that goal (Issue #2523)

Resolved: Defer this (word-break:break-word) to next level. (Issue #2390)
Resolved: Normatively state that text-transform does not apply to plaintext paste. (Issue #627)
Resolved: Make text indent percentage relative to the content box of the element. (Issue #2394)
Resolved: Requiring language for hyphenation to take effect. (Issue #869)
Resolved: Treat lone CRs as 0 width spaces. (Issue #855)
Resolved: Define hanging punctuation as scrollable overflow in all cases. (Issue #2398)
The group needed more time to look at current behavior for Issue #1597 (intrinsically-sized box with text-indent) so it will be covered on a telecon.
Resolved: Clarify spec to say control characters should be always visible even if fonts don’t provide a glyph. (Issue #1990)
Resolved: Defer this (font-relative letter-spacing) to text L4. (Issue #2165)
Resolved: Keep rule to collapse white space through bidi formatting chars, don’t mark at risk. (Issue #2233)
Resolved: Defer this (hanging-punctuation: last applying to colons and dashes) to L4. (Issue #2392)

Implementations are in progress for Animations and there were several pieces of implementor feedback discussed.
- The spec naming around timelines are currently all about time, but there’s interest in having it more about progress. However, it may be too late to change due to implementations that have shipped.
- Querying the main thread for state will be similar to how threaded scrolling.
- In Level 2 there is interest in exposing a web animation api to be used by javascript objects.
- The focus of Level 2 will be to offer extension points to the core specified in Level 1.
UA must implement coalescing for forward filling animations (Issue #2054)
Most people felt that returning the longhand to getKeyframes would be sufficient, though doing better would be nice.
Issue #2359 (Clarification about “make animation’s start time unresolved”) came from misreading of the spec, but raised a different problem that setTiming doesn’t do invalidation so a separate github will be opened.
There’s a desire to have a timeline attached to a media source but there are several possible solutions that need to be evaluated.

Resolved: Parse the value of src throwing out invalid parts like media queries and not like selectors. aka You split on the commas and throw out the pieces you don’t understand not the whole thing. (Issue #633)
Resolved: Use this: format(string[supports feature-name#]?) where feature-name is a CSS-defined identifier. (Issue #633)
An issue will be opened to determine if @supports for color fonts is necessary.
Resolved: Add an auto keyword to the appropriate font descriptors that has the effect of the following: 1) for font selection purposes the font is selected as if the appropriate initial value is chosen. 2) for variation axis clamping, clamping does not occur. (Issue #2485)
Resolved: Leave font-style computed values as-is; change font-style animation behavior so that ‘normal’ can animate with ‘oblique num’ (Issue #2505)
Resolved: Use 14 degrees as the angle for undefined oblique. (Issue #2295)
Resolved: Defer font-variant descriptor to L4. (Issue #2531)

Resolved: Use from-font [for text decoration metrics] (Issue #2376)
Resolved: Add this value [text-spacing:space-first], suggest it’s the default in epubs and add a open issue wondering if should be in the web in general. (Issue #2462)
There was general consensus that the property for paragraph-level line breaking should be a modifier on wrap not a separate keyword, but the name still needs to be bikesheded. (Issue #672)

Florian gave a brief introduction to the document of Ruby recommendations from Kobayashi-sensei. The document is available here and would be a good guide to Ruby editors.