Minutes Berlin F2F 2018-04-10 Part II: Spacial Navigation, CSS Floats, Grid L2, Grid L1, Box Alignment
Spacial Navigation
- Jihye showed a demonstration of how the spec has progressed so far (available here)
- Much of the current spec isn’t about CSS, but it has raised questions about terminology and making it easier to refer to scrolling concepts.
- It was suggested that all the definition of terms occur in CSS Overflow to make it easier to reference terms.
- There’s significant interest in having this spec assist accessibility concerns.
- The group did not think that adding information about hit testing would be valuable.
- Exposing a new Media Query that would give data on interaction media feature navigation raised concerns about possible fingerprinting. If there are strong use cases the group will reconsider.
- Resolved: Add the definition of the border shape edge to Borders and Backgrounds L3 (Issue #2324: Missing box terminology).
Full Meeting Minutes || Specs Referenced: Spacial Navigation, Backgrounds & Borders, CSS Overflow
CSS Floats
- Originally there were three proposals to address issue #2452 (What happens when a bfc height grows such that it intersects with a lower-placed float that was not considered when choosing its width):
- Attempt all possibilities until one fits (what Firefox does)
- If it doesn’t fit you try one more layout
- Put the BFC under the floats (what Edge does)
- Option 3 is the most performant, but option 1 was what users would expect. Option 2 was a compromise, but since no one implements it currently there were objections to resolving on it.
- The group agreed on Option 1 and will request more performance data from whomever implements so that they can re-open this if there is a significant performance issue.
- Resolved: The working group preference is to specify BFC float avoidance behavior to match the guidelines of what is spec in 2.1 for inline layout float avoidance behavior.
- Resolved: Start a CSS 3 Floats Module with dbaron and fremy as co-editors.
Full Meeting Minutes || Spec Referenced
Grid L2
- Author expectations and use cases were toward having the per-axis subgrid (Issue #2280) however several people needed more time to review the spec text so the group will revisit this issue later in the F2F.
- Resolved: Add an ar unit to the grid 2 spec for
align-content
and justify-content
. (Issue #1116)
Full Meeting Minutes || Spec Referenced
Grid L1
- The group believed that the Grid algorithm could still be adjusted to accomplish the use case in issue #2356; however the correct adjustments weren’t immediately clear. TabAtkins and fantasai will look into a post-processing step that was suggested and Florian will reach out to Bert to see if he has any insights.
- Resolved: Edit in Rossen proposal in issue #2177 “Spanners that cross tracks that have content-based mins AND flexible maxes only contribute content sizes to those tracks; otherwise they participate normally.”
- Resolved: Alignment and gaps in multicol behave exactly like grid and we will add a note explaining the concerns in the issue and how to solve them. (Issue #1420)
- Resolved: Remove these terms (
row-axis
and column-axis
) from the grid spec (Issue #1299)
Full Meeting Minutes || Spec Referenced
Box Alignment
- Resolved: Zero out percentages on non-sizing use of calc. (Issue #2297)
- Resolved: Fallback alignment for last-baseline is ‘safe end’ (Issue #1611)
- Resolved: Publish a new WD of Alignment with the one edit from the baseline resolution.
Full Meeting Minutes || Spec Referenced
« Previous article
Next article »