CSS WG Blog – Minutes Paris F2F 2017-08-03 Part I: Tables, Automating Test Coverage, CSS UI, F2F Scheduling

Minutes Paris F2F 2017-08-03 Part I: Tables, Automating Test Coverage, CSS UI, F2F Scheduling

By Dael Jackson September 2, 2017 (Permalink)
Categories: resolutions

Resolved: All internal table displays on replaced elements to behave as ‘inline’.
Resolved: ‘display: table’ on replaced elements behaves as block, ‘inline-table’ behaves as inline.
Resolved: Ignore percentage min-widths on table cells.
Resolved: Accept proposed resolution for #474:
- During the first layout pass:
  - neither table nor tr nor td has height -> they behave as auto
  - else if overflow:scroll|auto -> they resolve to “0px” (webkit+gecko webcompat)
  - else -> they resolve to “auto”
- During second pass:
  - neither table nor tr nor td has height -> they behave as auto
  - else they resolve based on row’s final height
Issue #484 (excess width distribution in fixed layout mode) needs web compat data checked before resolving.
Resolved: Cells spanning collapsed rows/columns are clipped to their resulting bounds (in both axes).

gregwhitworth proposed finding a way to automatically link tests to a section to make it easier to review all tests. The problem is that specs are not static. fantasai listed various approaches that have been tried: there is no ideal method, so the plan is for each spec’s QA owner to experiment.
This raised a larger question how to better test specs. There was interest in having an assigned QA resource per spec but ultimately that would require a commitment from WG member companies to send QA resources to the group.
Resolved: Changes list for a CR links to updated or additional test cases for each change.

Resolved: Close Issue #1598 as no change.
Resolved: Clarify in level 3 that the UA should dispatch events as if ‘text-ellipsis’ were ‘none’. (Issue #1637)
Resolved: Add informative note that links to the part of HTML that specifies how cursor works on image maps. (Issue #1618)
Florian will investigate if any SHOULD sections ought to become MAY sections since they’re failing in most/all major browsers.
Resolved: Move directional navigation properties, nav-up/down/ left/right to next level

Resolved: Put a note into “appearance” saying it’s not ready to implement, list the possible solutions discussed here, ask impls which they want to do. (Issue #1250)