Minutes Telecon 2024-03-13
- Resolved: Add a mutable .typeList to the VT object (Issue #9542: Allow changing `types` using JS after (MPA) transition started?)
- Resolved: Close no change (but add a note with some guidance) (Issue #9526: Behavior of mismatching types between old and new document)
- Resolved: :active-view-transition / :active-view-transition-type(`ident`) (Issue #9972: Rename :active-view-transition() pseudo-class)
- dbaron introduced issue #9458 (Need to better define how transform affects scrollable overflow) in order to get additional comments on the issue as they work toward a definition to rectify the discrepancy in definitions.
- Resolved: Accept this merged PR, re-add the fingerprinting sentence to the privacy/security section and an inline issue in the prefers-reduced-data section, and open a new issue on it to more thoroughly discuss it (Issue #9475: prefers-reduced-data question: special behavior when turned off and on post page load?)
- Resolved: We’ll fix the problems in this issue, details TBD (Issue #9917: Snap point selection when scrolling into view should try to make targeted element visible)
Full Meeting Minutes
Minutes Anchor Positioning Breakout 2024-03-13
- Resolved: rename anchor-default to position-anchor (Issue #10004: Rename `anchor-default` to `position-anchor`)
- TabAtkins will open a new issue about resetting of `position` shorthand
- Resolved: Add position-visibility as proposed in the issue with concerns noted as issues in the draft, to the editors draft *after* publication of working draft (Issue #7758: Need ability to say “don’t render” when anchor is off-screen)
- Resolved: Publish an updated WD of anchor-positioning
Full Meeting Minutes
Minutes Anchor Positioning Breakout 2024-03-06
- Resolved: Specify how styles that are conditionally dependent on layout get recomputed (Issue #9598: Fixing the animation problem)
- Resolved: We will use the same sort of recomputed values for animations on anchor & anchor-size functions (Issue #9598)
- Resolved: Accept that inset area changes the containing block (Issue #9598)
- Resolved: Defer magic position animations until level 2 (Issue #9598)
- Resolved: switching center-* keywords to span-* and all to span-all (Issue #9862: Can we clarify the `inset-area` syntax? It can be confusing to read and reason about)
- Resolved: Layout containment contains anchor names and size containment/paint containment do not (Issue #9349: Should size/layout containment also contain anchor names?)
Full Meeting Minutes
Minutes Telecon 2024-03-06
- Resolved: Make semicolons an optional upgrade to commas in CSS functions (Issue #9539: Better handling of arguments with commas)
- Resolved: No change, keep with the existing resolution [existing resolution] (Issue #6026: Use of 100vw is causing pointless horizontal scrollbars on some websites)
- Resolved: Custom properties don’t apply to the highlight pseudos. On highlight pseudos, the var() function takes from the originating element (Issue #9909: Revisit CSS Custom Properties in highlight pseudos)
- Resolved: If a content-visibility:auto element is skipping its contents but has not yet determined its visibility, don’t fire the `contentvisibilityautostatechange` event until you do know the visibility (Issue #9803: Should the first `contentvisibilityautostatechange` event be fired without knowing if the element is close to the viewport)
- Resolved: All of the text spacing properties don’t apply to the squished-together character of text-combine-upright; text-spacing-trim is treated as trim-all (Issue #9423: Spacing within text-combine-upright)
Full Meeting Minutes
Minutes Telecon 2024-02-28
- There is a proposed update to the contribution guide which clarifies when to land a PR. Group members are encouraged to review and make changes/give feedback.
- Though the group is still waiting on use counters for issue #8738 (Figure out whether we’re fine with “shifting up” bare declarations after rules), they agreed to start work on a design for if the use counters come back saying a change is possible.
- Resolved: Allow the modulus parameter to be optional in the case of rounding numbers and default to 1 (Issue #9668: Let B default to 1 in `round(strategy?, A, B)`)
- Resolved: -0% serializes to a normalized form (Issue #9750: Clarifying serialization of negative zero and expression simplification)
- Resolved: Not going to use the pixel unit for the pixel value in border-image-slice (Issue #6739: Accept “px” for pixel values in `border-image-slice`)
- Resolved: Close the issue in favor of consistency and reopen issue #5984 (Issue #7947: Should not cq units be interpreted in the flatDom context?)
- Resolved: Change CSSViewTransitionRule .type to .typeList (Issue #9905: `CSSViewTransitionRule.type` overrides deprecated `CSSRule.type`)
Full Meeting Minutes
CSS Text 4 Draft Updated
The CSS Working Group has published an updated Working Draft of CSS Text 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.
This is a fairly minor update, mostly focused on refinements to the text-spacing-trim property, which should be of interest for CJK typography. 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 2024-02-07
- Resolved: Overflowing into the gutter of a classic scrollbar triggers scrollable overflow, overflowing into the gutter of a overlay scrollbar does not trigger scrollable overflow (Issue #5253: Overflow into the gutter)
- Resolved: Drop scrollbar-gutter: force (Issue #9815: Subgrid obviates the need for `scrollbar-gutter: force`)
- There needs to be more use case discovery for issue #3871 (Detect physical keyboard (keyboard capable of shortcuts?)). On the call games were mentioned as a potential use case, but also concerns about fingerprinting and needing to tell the user so they can opt to add a keyboard.
- Resolved: Add window-focus: active | none, bikeshed later (Issue #5828: active vs inactive window states)
- Resolved: Add window-focus: active or none matching behavior of javascript in print behavior and matching (Issue #5828)
- Resolved: Align canonical order of outline sub-properties with border (Issue #7700)
- Resolved: The caret animation is auto versus none (Issue #9707: Inteference with the caret blinking and the ability to animate its color)
Full Meeting Minutes
Minutes Telecon 2024-01-31
- Resolved: Adopt triage Service-Level Objectives (SLOs) (Issue #9820)
- Resolved: Keep view-transitions l2 as a leveled delta spec (Issue #9850: Consider a living-standard model for view-transitions)
Full Meeting Minutes
Minutes Telecon 2024-01-24
- Resolved: Specify outline as ink overflow (PR #9824 | Issue #8649: Specify extent of ink overflow)
- Resolved: Alignment on scroll containers results in same layout as non-scrolling containers, and doesn’t affect whether initial scroll position is zero-coordinate, just changes which direction and how far you can scroll (Issue #4957: What is supposed to happen to abspos in an end-aligned scroll container?)
- There was more discussion to be had about testing for issue #9508 (Upgrade to Recommendation?) so discussion will return to github.
- Resolved: Choosing the innermost for textbox:trim for most requested trim metric (Issue #5426: text-box-trim accumulation)
- Resolved: ink-overflow spills out of the page content area into padding and margins, user agents that can’t draw ink overflow may shift content down to avoid clipping (Issue #5335: text-box-trim vs fragmentation)
- Resolved: Should text-box-trim apply at fragmentation breaks, depend on the box-decoration-break property (Issue #5335)
Full Meeting Minutes
Minutes Telecon 2024-01-17
- Resolved: Create & publish FPWD for css-viewport-1
- Resolved: Adopt picture-in-picture media query (Issue #9260: Add display-mode for document picture-in-picture)
- Resolved: Remove requirement for the ua stylesheet rule for inverted-colors (Issue #9674: Inverted-colors media feature can cause problems on semi-transparent images)
- Resolved: No change to :has() behavior (Issue #9422: Is it intentional that :has(:is()) is different from :has()?)
- Resolved: Close issue #5684 (What is the reasoning for ignoring default namespaces only on the subject for :is() / :where() / :not()?) with no change
- Resolved: Contextually-invalid selectors have a specificity of zero (Issue #9600: Specificity of contextually-invalid selectors)
- Resolved: Add ScrollIntoView to the definition of relevant to the user, should also affect ancestors (Issue #9337: ScrollIntoView a descendant of element with content-visibility:auto)
Full Meeting Minutes