CSS WG Blog – Minutes Burlingame, CA F2F 2017-11-06 Part II: Flexbox, Image Decoding, Line Clamping, Cleaning up OWNERS files, Feedback on Testing Policy, Values & Units, Contains, Line Grids, Line Heights

Minutes Burlingame, CA F2F 2017-11-06 Part II: Flexbox, Image Decoding, Line Clamping, Cleaning up OWNERS files, Feedback on Testing Policy, Values & Units, Contains, Line Grids, Line Heights

By Dael Jackson December 10, 2017 (Permalink)
Categories: resolutions

dholbert will investigate the Firefox code around sizing images and add more details on their implementation to the issue. His comment is available here.

smfr introduced the group to the proposal to expose an API to control background decoding of images. The proposal is available here.

There were two points of discussion, how to address the existing desire to have some of webkit-line-clamp and, if so, how to extend that further.
The desire is to have a concrete proposal for a webkit-line-clamp like property to further discussion.

Anyone listed on an OWNER file who won’t be reviewing tests was asked to do a PR and remove themselves.
There was some interest in a bot to notify of unreviewed tests.

The group spent time discussing how the resolution to require tests for CR+ spec has been doing in practice.
There was a desire to see a bit more nuance in the definition to have the tests become required once there is one implementation, to exclude editorial changes, and to clearly not require testing every possible variation, but to instead be a general test.
Additionally, there was a desire to add teeth to the policy where changes are not merged into the main until there is a test. However, several people were concerned that that requirement would cause changes never to be merged in instead of the intended addition of tests.

Resolved: Use principal box as the box to which we do paint containment clip. (Issue #1809)
Discussed whether style containment should be affecting pagination controls within the element. Tab will clarify what style containment is supposed to accomplish in principle so that this issue can be resolved accordingly.
Resolved: Create new counter scopes at style scoping root for style containment.
The suggested way to address issue #1457 would be that ‘contain’ would apply to neither inline nor ruby.

The group reviewed dbaron’s proposal to comprehensively address line spacing.
The group wanted to make sure that it covered all necessary use cases, but a preliminary pass suggested it would.
No one was ready to completely replace existing spec test with this proposal, but it will be used when attempting to fix the current spec.

Resolved: Take florian’s proposed change to definitive line heights. (Issue #1801)
Resolved: Take florian’s proposed change for line-height normal (Issue #1802)
Resolved: To define first available font more strictly in the fonts model and leave it undefined in 2.1 (Issue #1798).
Resolved: Change the wording such that 2.1 is saying you should define the content area based on the first available font and only that font. (Issue #1804).