Minutes Telecon 2023-11-29
- Zoom will be specified in the Viewport spec
- Resolved: getComputedStyle() returns unzoomed value so that it round-trips (Issue #9398: Zoom and CSSOM)
- Resolved: APIs that return bounding boxes such as getClientRects and getBoundingClientRect and IntersectionObserver return values in page-global px unit coords (Issue #9398)
- Resolved: font-size is not special wrt zoom (Issue #9397: Zoom and inheritance)
- Resolved: All computed absolute lengths are zoomed when inheriting (Issue #9397)
- Resolved: If overflow:scroll is set on the root element (not propagated from body), account for the default scrollbar width in the size of vw. Also take scrollbar-gutter (and scrollbar-width, the property with “normal” and “thin”?) into account on the root. Ignore all of these in MQs. And also ignore all of these when using vw/vh units on the root element, if necessary (Issue #6026: Use of 100vw is causing pointless horizontal scrollbars on some websites)
Full Meeting Minutes
Minutes Telecon 2023-11-22
- Resolved: Add View Transitions 1 to “fairly stable” in Snapshot 2023 (Issue #9577: Move CSS View Transitions to “fairly stable” in CSS 2023)
- Resolved: Publish Snapshot 2023 with View Transitions 1 moving to fairly stable and css-scroll-snap moving to rough interoperability (Issue #9566: Finish up CSS Snapshot 2023)
- Resolved: Republish snapshot 2022 as Group Note (not Draft Note)
- Resolved: view-transition-name is discretely animatable (Issue #9619: Is view-transition-name discretely animatable?)
- Resolved: :active-view-transition(*) has specificity of 1 class, :active-view-transition(list) has specificity of 2 classes (Issue #9546: :active-view-transition() specificity)
- Resolved: Accept some form of masonry slack property; exact algorithm TBD; exact name TBD (Issue #9328: Reordering threshold)
- Resolved: Though it was clear how Masonry would handle `auto-repeat` accepting intrinsic sizes, it was more uncertain if it could work in Grid. Discussion will continue in issue #9321 (Allow `auto-repeat` (i.e. repeat(auto-fill|auto-fit, …)) to accept intrinsic sizes) to understand further how it could be added to Grid.
- Resolved: Restore text simplifying out single-argument min/max functions (Issue #9559: Simplification algorithm should possibly return single child for min/max)
Full Meeting Minutes
Minutes Telecon 2023-11-15
- Resolved: Add mirror value to edgemode attribute (FXTF Issue #527: Add edgemode=reflect)
- Resolved: Define plus-darker based on research results in the issue and raise issue to deal with max/min in various cases (FXTF Issue #447: Remove or fix definition of plus-darker)
- Resolved: Create ED of css-contain-4 with all editors of css-contain-3 as a diff spec (Issue #6402: Define a syntax for state-based container queries)
- Resolved: Add sticky, snap, and overflow as new container type values (Issue #6402)
- Resolved: Better define this behavior when you have nested snap areas and children with interleaved content from the parent (Issue #9187: Improve or clarify nested snap behaviors)
- Resolved: For sticky pos, getComputedStyle will return computed values for insets (Issue #9267: Further restrictions on resolved values for insets?)
- miriam introduced an outline of the proposal to add color-mix(), calc-mix(), and progress() to CSS Values (Issue #6245: Interpolate values between breakpoints). In a future meeting to group will work toward resolution on these proposals.
Full Meeting Minutes
Minutes Telecon 2023-11-08
- The group will make a final decision on dates next week after coordinating with the AB meeting which is targeting a similar time frame.
- Una introduced the community group that is working on helping people understand and communicate about CSS by introducing naming conventions that are clear and support discussion needs. The presentation is available here.
- Resolved: The CSSWG supports this CG’s efforts in defining levels for CSS as a way for the community to understand and communicate about batches of CSS features. (Issue #4770: Let’s Define CSS 4)
- Resolved: type can accept any idents, except ‘none’ or ‘-ua-‘ prefixes (Issue #9534: Resolve on descriptor/parameter names)
- Resolved: at-rule is @view-transition, descriptors are ‘navigation’ and ‘type’, ‘navigation’ grammar is “auto | none” (‘type’ grammar already resolved) (Issue #9534)
- Resolved: A startVT() called on the new page will force-finish an MPA VT even if a frame hasn’t painted yet. (startVT() late in the old page is still undefined) (Issue #9512: Starting a same-doc view transition while a cross-doc view transition is pending)
- Resolved: startVT() on the old doc is ignored if there’s an active MPA VT running, but its callbacks are still dispatched (Issue #9512)
- Resolved: Change backdrop-filter’s edgeMode to mirror, pending any objections (FXTF Issue #374: Backdrop filter clipping with edgeMode=”duplicate” creates discontinuity when moving)
Full Meeting Minutes
Minutes Telecon 2023-11-01
- Resolved: Adopt the naming scheme for future values and as aliases for existing values (Issue #9487: checkVisibility options have inconsistent naming schemes)
- Resolved: Revert the previous resolution and the serialization for spec value is a 3-value serialization (Issue #2274: Inconsistent position serialization)
- Resolved: Define how new and old viewport units interact and that old units are equivalent to large viewport units (Issue #6454: Restrictions on UA-default viewport units (unprefixed v*))
- Resolved: We define relationship between ICB, abspos, and fixedpos and viewport size as detailed in the comment (Issue #6453: viewport units vs initial containing block)
- Added Brandon Stewart as an editor to CSS Masonry spec.
- Resolved: Add row-reverse, column-reverse, and wrap-reverse (Issue #3622: Add more directional values to grid-auto-flow)
- Resolved: Add two numbers to the repeat function that when used with one of the keywords define a range (Issue #9325: Repeat range)
- Resolved: ::backdrop is a tree abiding element. It’s tree is a sibling of the root tree. It inherits from its originating element (Issue #7845: Define ::backdrop)
- Resolved: ::backdrop does not have a ::before and ::after (Issue #7845)
- Resolved: Remove the claim that outline-width influences the rendering of auto style outlines (Issue #9201: Influence of outline-width on auto style outlines)
- Resolved: @container rule can have just a container name and match the closest container with that name (Issue #9192: Make `container-query` optional in `@container`)
Full Meeting Minutes
CSS Text Level 4 Draft Updated
The CSS Working Group has published an updated Working Draft of the CSS Text Module Level 4.
This CSS module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.
The most notable changes since last publication are:
- The
text-wrap property has been recast as a shorthand of two new properties, text-wrap-mode and text-wrap-style, and made text-wrap-mode rather than text-wrap a longhand of the white-space property. We call on implementations, particularly those that shipped text-wrap: balance, to be updated to match this new shorthand and longhand relationship.
- The
word-boundary-detection property has been retired; phrase based line breaking is now controlled by word-break: auto-phrase, and phrase-based space insertion by the auto-phrase value of the word-space-transform property.
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-text-4]) 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-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
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: