CSS WG Blog – Minutes Berlin F2F 2018-04-12 Part II: CSS Tablets, Text L3, Overflow L3, CSS Contain, CSS 2.x, Testing

Minutes Berlin F2F 2018-04-12 Part II: CSS Tablets, Text L3, Overflow L3, CSS Contain, CSS 2.x, Testing

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

Resolved: Spaces don’t hang when break-spaces is specified (Issue #2465)
Resolved: We should define what an alias is in CSS Cascade. (Issue #866)
Resolved: We will make the required edits for the definition resolved previously. (Issue #866)
Resolved: We create a new legacy shorthand concept in Cascade L4 for those things that we have legacy shorthands that should never be serialized. (Issue #866)
Resolved: Everything that’s currently defined as an alias needs to use new legacy definition or is a legacy shorthand. (Issue #866)

Resolved: Require that you leave space in scroll containers for block-end padding in the scrollable area. (Issue #129)
Resolved: Undo the previous resolution and continue to figure out a whole model. (Issue #129)
When discussing Issue #129 (padding-bottom in overflow content) the group originally thought they could solve the bigger author pain point (block-end padding) in isolation. However, as conversation continued it became clear that an entire modal that covered inline padding and the relationship to absolutely positioned elements was required to address this issue.

Resolved: You’re allowed to have forced breaks inside a layout contained thing but you can’t propagate the break to the parent. (Issue #2527)
Resolved: Elements with size containment are monolithic for the purpose of fragmentation. (Issue #2527)
After the resolutions from the F2F are edited in the authors will request an updated CR publication.

Resolved: Accept this new editing process (documented here)
Resolved: Use the naming scheme proposed at bottom of the proposal
Resolved: Ask the team to make https://www.w3.org/TR/REC-CSS2 redirect to https://www.w3.org/TR/CSS2

The group discussed what it would take to move to WPT tests and, though there were plenty of pain points listed, the only commitment was from TabAtkins to continue improving bikeshed integration.
- Some of the pain points mentioned:
  - Manual tests put a lot of pain on the tester
  - Ahem font not installed for Edge invalidates most of those results
  - Lack of controls over shared files to prevent breakage when changes are made
  - Not exporting tests in a way the test harness can import
  - Needs fuzzy matching for ref tests
  - No good way to flag/differentiate ‘may’ and ‘should’ tests from ‘must’
Documentation for testing was also discussed (Issue #2438) and the group come up with several recommendations:
- Use the testing wiki to guide new testers and browser vendors since the WPT documentation is too high level for that audience
- Don’t re-write documentation that exists on WPT but instead link to it
- Add search to the WPT documentation