CSS WG Blog – Minutes Toronto F2F 2019-06-04 Part II: CSS Fonts; CSS Multicol; CSS Sizing; CSS Display and UI

Minutes Toronto F2F 2019-06-04 Part II: CSS Fonts; CSS Multicol; CSS Sizing; CSS Display and UI

By Dael Jackson July 6, 2019 (Permalink)
Categories: resolutions

Resolved: Remove min-font-size and max-font-size from Fonts 4, replace with an example of using clamp() to handle safe responsive typography. (Issue #3739: font-min/max-size and computed value)
A note will be added to Fonts spec about the font-size: 0px vs min font-size web-compat issue
Resolved: Capture that font-size keywords carry an additional bit of information having some (unspecified) interaction with some font families. (Issue #3906: Clarify how computed font-size is determined for size keyword)
Resolved: François does compat research on the effect of font-size keywords and generic font-families, and report back on interop. (Issue #3906)

Discussion on the request to add math-script-level and math-style properties to CSS (Issue #3746) became a wider topic about the best way to support math on the web.
- There is a request for more examples and more of a sense of scope of the larger issue leading to these properties to allow the group to ensure that they’re building properties in the right way.
- Without the full understanding it’s unclear if some aspects of this, e.g. the ‘script level’, need to be encoded as information in the DOM rather than in CSS (so that they can be selected against).
- CSS and the MathML group need to establish a standard approach to communication going forward so that specs can stay aligned.
Before any final decisions the meta topic of the future of MathML needs to be addressed. There are three possible futures that need to be evaluated in order to decide the path forward:
1. MathML is in browser engines, CSS has to be compatible with what it is.
2. MathML is in browser engines, but we might make substantial changes as we develop and can adjust it to fit with CSS better.
3. MathML isn’t the right path forward, and math should be taking a new path forward.

Resolved: Column-gap percentages no longer at-risk. Add some tests to WPT. (Issue #3988: Remove at-risk marker for percentages in column-gap)
Resolved: Keep a section to explain how column-gap works in multicol, but define in box-alignment only (and link between them) (Issue #3641: Should we refer to definition of `column-gap` in Box Alignment?)

Resolved: cbiesinger will document Chrome’s behavior and we will revisit (Issue #3973: Why was min-content redefined to do nothing on the block axis?)

Resolved: Outline of ‘display: contents’ is propagated to children for painting (for a11y on focus); implementers should give feedback on it (Issue #3323: Should outline apply to elements with display:contents)

Last updated 2019-07-06 22:20:39