Minutes Telecon 2023-04-26
- Resolved: FPWD CSS Positioned Layout L4
- Resolved: No change to current spec. Draft ability for a counter function to return the counter string including prefix/suffix, with various fallback options (Issue #8619: Should fallback use prefix/suffix of original style or fallback style?)
- Resolved: Accept proposal to match JS scinot serialization triggers, other than 6-digit decimal truncation rule (Issue #8538: Serialize numbers using scientific notation?)
- Resolved: Update CSSOM to allow null representation of imported style sheets (Issue #8608: CSSImportRule.sheet not being null conflicts with @import supports())
- Resolved: Accept IDL in issue (Issue #8710: Extend CSSImportRule to expose supports condition)
- There are three possible locations for the F2F. The group is asked to provide feedback on the private list as to how likely they are to attend the three candidate locations on the week of July 17th or the week after.
Full Meeting Minutes
Minutes Telecon 2023-04-19
- Resolved: Specify `@initial` as defined in this issue and open another issue about the duplication problems with entry and exit styles (Issue #8174: Add pseudo-class to establish before-change style for css-transitions on new elements)
- Resolved: Start with the name `@starting-style` instead of `initial` (Issue #8174)
- Resolved: Close issue with no change (Issue #7795: checkVisibility and filter:opacity(0))
- Resolved: Close, no change (Issue #8259: Define optimizeSpeed as nearest neighbor)
- Resolved: If there are no valid options, render as an invalid image (Issue #8266: Define what happens when all image-set options are invalid)
- Resolved: Math function simplification for descriptors is as if they were specified properties, and descriptors with math functions use the specified-value serialization rules (Issue #7964: Unclear serialization of calc expressions in `@font-face` font-stretch/style/weight descriptors)
- Resolved: Remove slider-horizontal, square-button, and push-button from `compat-auto`; PaulG will open an issue about ARIA roles and concerns about slider-vertical and push-button (Issue #8506: Consider removing slider-horizontal from `compat-auto`)
- There are questions about the relationship between overflow-anchor and the proposed new `always` value on issue #7745 (Consider adding an opt-in way of avoiding scroll anchoring suppressions). Discussion will return on github to come up with a proposal.
Full Meeting Minutes
Minutes Telecon 2023-04-12
- Resolved: Change getCurrentTime() parameter to a dict to satisfy Brian’s/the TAG’s concerns (Issue #8201: Animation.getCurrentTime is easily confused with Animation.currentTime)
- Resolved: Times in a non-time-based timeline are converted to their relative percents (Issue #7749: Prefer phase based start / end delays over converting time based delays)
- Resolved: Once group effects are added, also add percent-based delays/durations (Issue #7749)
- Resolved: Draft up proposal for time-based keyframe selectors in Animations 2 (Issue #4907: Proposal: Time-based Keyframe Animations)
- Resolved: Define “snapshot CB” as the current snapshot root rect, give it ICB behaviors so it captures all elements (preventing them from going higher) (Issue #8505: Enforce ::view-transition to be fixed position)
- Resolved: isolation/blending-mode properties are added conditionally, as stated in current spec (Issue #7814: Should isolation and plus-lighter blending be applied conditionally)
- Issue #8542 (content-visibility: auto visibility check timing needs details) needs more consideration around handling of ResizeObserver and so discussion will continue on github.
- Resolved: Leave the values in Values Level 5 (Issue #1603: Define crossorigin, preload and async URL modifiers)
Full Meeting Minutes
Minutes Telecon 2023-04-05
- Resolved: Republish WD of css-highlight-api-1
- Resolved: If there is color in the author origin the UA must respect that color exactly, including its alpha (Issue #6853: Safari’s ::selection “wash” and UA tweaks to highlight colors)
- Resolved: If there isn’t a color from the author origin the UA may apply magic (Issue #6853)
- Input is needed from authors on issue #6641 (Custom properties on :root) to determine which option is the least bad based on the downsides they present.
- Resolved: Accept @sheet with URL fragment referencing rule. Exact details to be in the Cascade spec (Issue #5629: Multiple stylesheets per file)
- Resolved: Negative
resolution
values are invalid (Issue #8532: Specify argument range for resolution)
- Resolved: Spec it as undefined (Issue #8527: Consider removing asymptotic special-cases for tan())
- Based on the initial poll the target for a F2F will be the second or third week in July. The chairs will now look for a host in the east coast of the Americas. There will be a follow-up poll shortly to get more specific details about availability for travel.
Full Meeting Minutes
Minutes Nesting Breakout 2023-04-05
- Resolved: Redefine CSSRuleList as ObservableArray (Issue #8350: Consider using ObservableArrayCSSRule instead of CSSRuleList)
- TabAtkins will file issue about CSSStyleDeclaration’s array upgrade
- Resolved: If naked property declarations inside @media become a thing, they are wrapped in a & {} rule (Issue #7850: CSSOM for nested media query rules)
- fremy or plinss will file issue about whether naked declarations get sorted to the top of the list or not
- Resolved: Close no change (Issue #7803: Nesting conditional rules)
- We will retain the current spec behavior for issue #8399 (Feature detection for nesting) which is the bare & supports strategy.
- The lookahead proved viable for issue #8249 (Problem with mixing properties and selectors). Discussion will continue on github as to the final decision between the provided options.
Full Meeting Minutes
Minutes Telecon 2023-03-29
- Resolved: Accept the CSSScopeRule design, with the three changes noted in the thread (Issue #8626: What is the desired shape of CSSScopeRule?)
- Resolved: Add break-spaces to white-space-collapse (Issue #3794: white-space:break-spaces is in level 3 but not level 4)
- Resolved: Accept the proposed addition to the ‘white-space’ grammar [addition is ‘white-space-collapse’ || ‘text-wrap’ || ‘white-space-trim’ as values for white-space shorthand] (Issue #5382: Multi‑value `white‑space` syntax proposal)
- Resolved: Snapshot raster is theoretically infinite. Snapshot has a “natural view box” of the snapshot element’s border box (giving the natural size). Object-view-box can change this view box (Issue #8597: Exposing ink overflow rect bounds to script)
- Resolved: Closed invalid, fixed by the #8597 resolution (Issue #8606: Clarify the size of snapshot when there are nested transitioning elements)
- Resolved: Add :popover-open pseudoclass, undefined popoverness from :open (Issue #8637: Introduce `:popover` pseudo class)
Full Meeting Minutes
Updated CSS Text Level 4: Refactored text-spacing and white-space Shorthands
The CSS Working Group has published an updated Working Draft of CSS Text Level 4. This module covers covers white space processing; line breaking; text spacing, justification, and alignment; and text transformation.
This update significantly refactors the text-spacing
property, completes the refactoring of white-space
into shorthands, and renames its text-space-*
longhands back to white-space-*
. Changes since the last Working Draft are detailed in the Changes section.
We encourage everyone to review the syntax and behaviors of these two shorthands and their longhands, since several implementations are currently in progress:
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-03-22
CSS Cascade
- Resolved: Cascade proximity is weaker than specificity (Issue #6790: Strong vs weak scoping proximity)
- Resolved: The combinator is deferred (Issue #8628: Do we want to defer some or all of these scope extensions to level 7?)
- Resolved: The name will be @scope-siblings (Issue #7751: Handle sibling-proximity in @scope)
CSS Animations
- Resolved: Include `overlay` property with values of `auto` and `none` to position-4 with a note about concerns over extensibility (Issue #8189: Entry and exit animations for top-layer elements)
CSS Contain
- Resolved: Elements within a display:none subtree have no parents that container queries can access (Issue #8197: Container queries within display:none are difficult to implement)
- Resolved: Add a function for every container query unit that allows to reference a named container (Issue #7858: Reference named containers for cq units)
- Resolved: Style queries can accept properties in boolean context; false if matches initial value, true otherwise (Issue #8127: Allow container query style features to evaluate in a boolean?)
- It’s unclear if the questions in issue #7875 (`overflow: auto` incompatible with size containment and container queries) are covered in the spec and need clarification or if there are changes to be made to handle contain-intrinsic-size.
CSS Color
- Resolved: Allow out-of-gamut HSL and HWB colors (Issue #8444: Allow out-of-gamut HSL/HWB colors (previously “Move gamut mapping to a future spec”))
- Resolved: Change specification say browsers MUST use OKLab color interpolation for all colors, including legacy colors (Issue #7948: What if legacy colors *also* interpolated in Oklab by default?)
Full Meeting Minutes
Minutes Telecon 2023-03-20
Scroll Animations
- Resolved: Reduce default scoping to ancestors only, add scroll-timeline-attachment as described in the issue (Issue #7759: Broader scope of scroll timelines)
- Resolved: Collapse keyframes with same specified offset to the earlier one, then pull percentage-only keyframes to the front and sort them (Issue #8507: Keyframe ordering and ordering requirements)
- Resolved: Accept proposal in the issue (Issue #8405: animation-range vs animation-duration)
- Resolved: Scroll overlap range is in addition to scroll-padding, view-timeline-inset should have an initial value of auto (Issue #7747: Consider initial value of auto for view-timeline-inset)
- Resolved: animation-range’s initial value is the keyword “normal” (Issue #8406: Naming the initial value of animation-range)
- Resolved: For printing/paged, root is considered fully in view (scroll timelines on it are inactive) (Issue #8226: Define scroll linked animation behavior in printing documents)
- Resolved: Percentages outside the 0-100 range are valid in progress percentages (Issue #8552: Clarify that progress percentages must be between 0% and 100%)
- Resolved: Make `percentage` optional in animation-range-start/end, defaulting to 0%/100% (Issue #8438: Allow optional `percentage` in `animation-range-*`)
- Resolved: When specifying “animation-range: foo X%”, set the -range-end to “foo 100%” (staying in same phase, just setting to end) (Issue #8438)
- Resolved: SLA uses logical interpretations of scrolling (rather than scrollLeft/Top always) (Issue #7752: ViewTimeline values of startOffset/endOffset in RTL writing mode)
- Resolved: Pending Brian’s potential objections, go with `getCurrentTime(rangeName?)` (Issue #8201: Animation.getCurrentTime is easily confused with Animation.currentTime)
- Resolved: SLA does do flat-tree lookup for nearest ancestor scroller, spec will be clarified (Issue #8192: Timeline lookup should probably not use flat tree)
- Resolved: New features are not added to the animation shorthand (for now), they’re just reset (Issue #8054: Animation short-hand support for new properties)
- Resolved: Merge keyframes if their *specified* offsets match, don’t try to merge based on computed (Issue #8487: Avoid merging named timeline range keyframes which compute to the same offset)
CSS Overflow
Full Meeting Minutes
Minutes Telecon 2023-03-15
View Transitions
- Resolved: If an element if fragmented into more than one element, it does not participate in View Transitions (plus note that we want to do such things in the future) (Issue #8339: Capturing fragmented elements)
- Resolved: If an element is involved in a transition, the `view-transition-name` constraints are enforced during the transition (Issue #8548: Define the constraints which must be satisfied by a named element during the transition)
- Resolved: Conditions are checked per-frame; transition is skipped if other constraints are broken (Issue #8548)
- Resolved: The view transition fills the viewport and captures clicks (Issue #8278: UA CSS should size ::view-transition to 0x0)
- Resolved: Target pointer events to the document element (Issue #7797: User input should be ignored when rendering is suppressed)
- Resolved: User agent can limit rasterization for performance limitations, but must size the element as if it was fully rasterized (Issue #8561: Define behavior when capturing image for a large element)
- Resolved: Rasterization must cover at least the visible area of the viewport (Issue #8561)
- Further discussion is required to determine how to handle painting overflow in issue #8561. There needs to be a bit more understanding of both author expectations and fingerprinting implications.
Full Meeting Minutes