CSS WG Blog Minutes Telecon 2022-10-12

Minutes Telecon 2022-10-12

• There will be an extended meeting on Wed Oct 26, 2022 from 7:00am – 10:00am PT
• Resolved: Incorporate trim-end behavior into the normal keyword (Issue #7055: text-spacing: trim-end is better than allow-end for the normal value)
• Resolved: Add text-justify:ruby, which is like ‘auto’ but disables justification opportunity on spaces and bopomofo (Issue #771: Treatment of multiple Latin words in space-between & space-around)
• Resolved: `rt, rtc { text-justify: ruby; }` to UA stylesheet (Issue #771)
• Resolved: `lang=und` matches :lang(“*”)`, `lang=””` doesn’t match any `:lang()` (Issue #6915: `:lang` for documents without content language and for elements of unknown language; consider `:lang(“”)` over `:not(:lang(“*”))`)
• Resolved: Accept :open and :closed with definitions as proposed by TabAtkins (Issue #7319: Add `:open` or `:top-layer` pseudo class)
  • Proposed definitions: The :open pseudo-class represents an element that has both “open” and “closed” states, and which is currently in the “open” state. Exactly what “open” and “closed” mean is host-language specific, but exemplified by elements such as HTML’s details, select, and dialog elements, all of which can be toggled “open” to display more content (or any content at all, in the case of dialog). Note: Being “open” is a semantic state. An element not currently being displayed (for example, if it is in a display: none container) can still be “open” and will match :open.
• The proposal for issue #7431 (Restrict none/auto/normal from custom-ident) was to restrict none/auto/normal from custom-ident however, after conversation, there is a desire to revisit in context of the overall custom-ident grammar to ensure this doesn’t make other naming issues worst.
• Resolved: Accept to make & valid everywhere, maps to :scope where not otherwise defined (Issue #7545: Move nest-containing and nest-prefixed selector definitions to Selectors)
• The group is going to think more about the possible use cases around issue #7340 (Allow ‘order’ on table columns) and decide next week if this is something they want to pursue further.

Full Meeting Minutes

« Previous article Next article »