Minutes Telecon 2023-10-18
- Resolved: Make the parameter non-nullable, but keep it optional (Issue #9460: Making the callback param non-nullable)
- Resolved: Extend checkVisibility to expose content-visibility: auto state (Issue #9474: API to expose skipped content state)
- Resolved: Close no change, reopen if use cases are presented on the issue (Issue #9478: What does element.checkVisibility() return for display: contents elements?)
- Resolved: We will address this issue, and fix nesting to allow for bare declarations after nested rules without moving them above (Issue #8738: Figure out whether we’re fine with “shifting up” bare declarations after rules)
Full Meeting Minutes
Minutes Telecon 2023-10-11
- Issue #9041 contains several issues with the masonry layout and how it would work with grid. They’ve been separated into individual issues for easier discussion and resolution.
- Resolved: Spec ‘continue: collapse’, add issue about whether ‘line-clamp’ invokes ‘discard’ or ‘collapse’ (Issue #7708: Is continue: discard working in the fragment tree useful?)
- Doing async polls as proposed in issue #9438 was overall successful in gathering data on preferences and surfacing new ideas and questions. The group is open to continuing to use them when appropriate to inform decisions.
- Resolved: Async polls should allow emoji reactions (Issue #9438)
- Resolved: Edit top comment to link to the poll (Issue #9438)
- Resolved: Open polls should be listed at top of agenda / proposed agenda emails as a reminder (Issue #9438)
- Resolved: field-sizing: content | fixed (Issue #7542: Allow ‘textarea’ to be sized by contents)
- Resolved: text-wrap-mode (Issue #9102: Move “balance | stable | pretty” out of text-wrap)
- flackr introduced issue #9187 (Improve or clarify nested snap behaviors) and showed the improved diagrams available to aid discussion. Group members were encouraged to review the issue and comment on github.
Full Meeting Minutes
Minutes Telecon 2023-10-04
- Resolved: At top level, if you see a rule that looks like a custom property, we consume as a rule and throw it away as invalid (Issue #9336: Dashed-ident rules and error recovery)
- TabAtkins will look into using a more generic term than ‘nested’ for the flag for mixed declaration+rule contexts for issue #9336
- Resolved: Straw poll for naming between -wrap and -allow. Values are wrap|nowrap (Issue #9102: Move “balance | stable | pretty” out of text-wrap)
- Resolved: Values will be fixed | content (Issue #7542: Allow ‘textarea’ to be sized by contents)
- The group will run a poll on form-sizing vs field-sizing, with values content and fixed for issue #7542.
- Resolved: Drop align-tracks, justify-tracks from Masonry spec (Issue #8207: Masonry – align-tracks / justify-tracks potentially not desirable for accessibility)
- Resolved: mask-border properties will match border-image wrt animatability (FXTF issue #529: Interpolation of mask-border properties)
- Resolved: mask-type is not a longhand of mask (FXTF issue #528: Is mask-type a longhand of mask?)
- The group will update “Animatable” lines to “Animation type” in all propdef tables (FXTF issue #521).
Full Meeting Minutes
Minutes Telecon 2023-09-27
- Nobody was enthusiastic about text-wrap-mode as the property name in issue #9102 (Move “balance | stable | pretty” out of text-wrap), and there was some concern about it being too similar to text-wrap-style to be easily distinguishable, but nobody had a clearly better idea. Discussion will continue in github for one more week before a final decision will be made.
- Resolved: Animate backdrop-filter for view transitions similar to transform/size (Issue #9358: Animate backdrop-filter for named elements)
- Resolved: Add accessibility non-treatment agreed up on at TPAC to the spec, stating the view transition pseudos are presentational and have no special accessibility needs (Issue #9365: Add a11y text to specify how VT works with it)
- Resolved: Fix the example and re-affirm the one-way containment of counters by instantiation of new counters (Issue #9212: Style containment for counters)
- Resolved: Add a clarifying note about the counter function and review the WPT tests (Issue #9212)
Full Meeting Minutes
Minutes Telecon 2023-09-06
- There was a new proposal for addressing issue #9166 (`contrast-color()` MVP in Level 5) which was designed as an in between option for the existing proposals which gives browsers some room to experiment toward an algorithm while giving authors predictability. Some concern was expressed that this new proposal will cause browsers to diverge their results so far that authors are unhappy or be so restricting that the browsers will only use white/black. In order to have this proposal work as an experiment toward an algorithm, it needs to be there from the beginning so it’s a default behavior which is what we’d want an algorithm to be if it’s successfully developed.
- Resolved: Function returns dark/light by default and the ‘max’ keyword for black/white (Issue #9166: `contrast-color()` MVP in Level 5)
- Resolved: Don’t add to CSS right now due to lack of use cases/user voices to add it (Issue #9293: Numeric separators)
- Resolved: Disallow the use inside container blocks (Issue #9280: Support for highlight pseudos declarations inside @container media queries)
- Resolved: Change the line about selection to link to the selection API instead of highlight pseudo element (Issue #9277: Should CSS highlights make content relevant to the user?)
Full Meeting Minutes
First Working Draft of CSS Transitions Level 2
The CSS Working Group has published an First Public Working Draft of
CSS Transitions Level 2. CSS Transitions allow property changes in CSS values to occur smoothly (or discretely) over a specified duration.
Level 2 (currently written as a delta specification, since Level 1 is not complete) introduces two new features:
- the ability to opt in to CSS transitions for properties or values that are animatable discretely (rather than only those that are animatable continuously), and
- the ability to specify a starting style for a transition to occur when an element changes from not being rendered to being rendered.
It also improves integration with Web Animations and defines a new
interface and other rules for that integration.
Changes since the last Working Draft are listed in the Changes section.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-transitions-2]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2023-08-30
- Resolved: Publish CSS Text 3 as a CRD
- Resolved: Accept the proposed resolution with the examples included (Issue #8318: Specified value for color when calc() is used)
- Resolved: Three longhand properties as proposed with two linked by a shorthand, names to be bikeshed, one issue for each to work them out (Issue #8829: It’s impossible to use `text-box-trim` without changing line progression within the paragraph)
- Resolved: Allow a single value for box-shadow-offset for that longhand property only (Issue #8568: Allow declaring `box-shadow-offset` with a single value)
- Resolved: We go with option 2 [add a stripe function family] and worry about composability in the future (Issue #7244: Allow stripes to be used as gradients)
Full Meeting Minutes
Minutes Telecon 2023-08-23
- Resolved: CSS Transitions 2 will have a FPWD
- Based on the discussion around issue #7387 (Providing authors with a method of opting into following the visual order, rather than logical order) the group is leaning toward removing reading-order: integer in favor of a more simplified approach. However, the newly proposed approach needs to be documented further to help work through the complications around reading order.
- Resolved: text-wrap becomes a shorthand for text-wrap-style and text-wrap-onoff, and only text-wrap-onoff is a longhand of white-space (Issue #9102: Move “balance | stable | pretty” out of text-wrap)
- Resolved: To use the actual displayed color when calculating contrast (Issue #8539: contrast-color() and gamut mapping)
- Resolved: Pursue this approach (an MVP of contrast-color()) in level 5 (Issue #9166: `contrast-color()` MVP in Level 5)
Full Meeting Minutes
Minutes Anchor Positioning Breakout 2023-08-23
- Resolved: Add border, padding, and margin properties to position fallback rules (Issue #9195: Allow more properties in position fallbacks)
- Resolved: Make the anchor-name property a comma-separated list of idents (Issue #8837: Ability for a single element to have multiple anchor names)
- Resolved: Add a separate property (can bikeshed name in future), not merely a shorthand, but interacts with inset properties in current draft (Issue #9145: Grid-based anchoring syntax?)
- Resolved: inset-area causes ‘auto’ keywords of inset to resolve to appropriate anchor() functions (TBD at computed or used value time) (Issue #9145)
- Resolved: Accept proposal in the draft with details to be worked out over time (Issue #9196: Alternative syntax for auto position fallback)
Full Meeting Minutes
Minutes Telecon 2023-08-09
- The group discussed the three options to address issue #8048 (Declarative Cross-document View Transitions) that emerged from the F2F. There was some pushback on using media queries, but not an immediate alternative so people will continue gathering ideas in the issue. Feedback on which CSS pattern to use for customization is particularly necessary.
- Resolved: Add light-dark() function that returns a color based on the color scheme (Issue #7561: Add a function to allow authors to specify colors reacting to `color-scheme`)
- Resolved: No (further) change (Issue #8629: Computed value and serialization of `Infinity` and `NaN` in color functions)
- Resolved: Close no change (Issue #8026: Add slashes between individual `border-color` values)
- Resolved: All ‘display’ values other than ‘none’ or ‘contents’ on ‘::backdrop’ compute to ‘block’ (Issue #7845: Define ::backdrop)
Full Meeting Minutes