Minutes Telecon 2024-03-27
- Resolved: We will use shaped edge and unshaped edge (Issue #5132: How to refer to the corner-shaped padding/border/content edges)
- Resolved: Editorial update to level 3 box rec
- Resolved: View Transitions level 2 to public working draft (Issue #10096: FPWD for CSS View Transitions L2)
- Resolved: Use FrozenArray for CSS OM. VT typeset which is setlike for types attribute. Keep sequence of strings for svt as is. (Issue #10114: Data type for types in script APIs)
- Resolved: Don’t deduplicate values in reflections (Issue #10114)
- Resolved: Don’t drop invalid values in reflections (Issue #10114)
- Resolved: Make * optional if you are using a class (Issue #9874: Consider allowing `::view-transition-group(.class)` without *)
- Resolved: All scroll containers default to unsafe alignment (not actually unsafe on scroll container) (Issue #10008: Default safety of scroll containers)
- Oriol introduced proposed syntax to specify the agreed upon behavior for list-time nesting in issue #9076 (list-item counter nesting is confusing). There were questions on handling defaults and if the property should inherit, but the group didn’t have time to discuss further on the call so conversation will return to github.
Full Meeting Minutes
Minutes Telecon 2024-03-20
- Resolved: Make CSSViewTransitionRule readonly (Issue #10011: Make CSSOM interface read-only)
- Resolved: Change use of DOMTokenList to something more appropriate for readonly interfaces (Issue #10011)
- Resolved: Switch to using “types” in all the locations (Issue #10070: ‘type’ argument that takes an array of types is very weird naming)
- Resolved: Use “InvalidStateError” when skipping the view transition due to document not visible (Issue #10101: Which skipping reason does “View transition page-visibility change steps” use?)
- Resolved: Fix algorithm error, always return transition object (Issue #10101)
- Resolved: Publish CRD of css-view-transitions-1
- Resolved: No change to spec for non-transparent colors (tests need fixing) (Issue #9851: How are the specified color used?)
- There were reasons to either pre-composite or ignore semi-transparent and transparent colors for scrollbars. The group did not have time to resolve so they will detail out the pros/cons in issue #9853 (What do (semi) transparent colors mean for scrollbar-color).
Full Meeting Minutes
Minutes Anchor Positioning Breakout 2024-03-20
- Resolved: Undo the previous resolution – anchor names are not blocked by any form of containment. But they *are* blocked from escaping a “skipped content” element (Issue #10040: Containment makes it difficult to use anchor positioning with container queries)
- Resolved: And if a positioned element is “relevant to the user”, any element it’s anchoring to remains “relevant to the user” as well (Issue #10040)
- Resolved: Fallback styles live in a new “Position Fallback Origin”. They revert like Animation styles (back to User origin) (Issue #9149: Define interaction with the cascade in `@position-try`)
- Resolved: !important is not allowed within position-try (Issue #10058: Is !important allowed in @position-try)
- Resolved: Forget if position-try CSS changes or any of the try blocks change (Issue #10099: When to invalidate “last remembered position-try option”?)
- Resolved: No change to spec (Issue #9245: border-radius and border-image should be “border properties”)
Full Meeting Minutes
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