Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.w3.org/blog/CSS below:

CSS WG Blog front page

By September 12, 2025 (Permalink)
Categories: resolutions

• The group discussed the possible ways to address the fingerprinting issue raised in issue #10372 (Mitigating fingerprinting for AccentColor/AccentColorText) A focus of the conversation was if tainting the color so it paints correctly but doesn’t return an exact value could address this issue. The potential path forward would be tainting by propagating a computed color plus an additional bit. Concerns were expressed that if the group couldn’t figure out how to get AccentColor/AccentColorText to paint correctly then the feature itself would not have value.
• Resolved: Change ‘direction’ to ‘scrolled’, discuss keywords later (Issue #12623: Disambiguate scrollable/direction when along axis/towards edge)
• There wasn’t disagreement with the proposal raised in issue #12652 (animation-trigger CSS syntax) to have the event or action be optional in the new trigger() property. However, there was still a lot of discussion on the broader syntax and bikeshedding so a resolution on this specific question felt premature.

Full Meeting Minutes

By Dael Jackson September 5, 2025 (Permalink)
Categories: resolutions

• Resolved: Change the definition to ‘must do nothing’ and make the computed value remain (Issue #12015: What to do with `blink` value in `text-decoration`?)
• Resolved: Change initial value of item-tolerance to ‘normal’ (Issue #12111: Make `item-tolerance` initial value `normal`)
• The group discussed the options in github for issue #12176 (Giving ::scroll-marker-group a name (and optionally text))
  • There was disagreement about if this type of labeling is the scope of CSS or the scope of HTML. :before and :after allow the labeling so there is a precedent, however a11y guidance is away from that use case so it’s unclear if it’s a path that should be followed.
  • General questions about scroll markers being in CSS were also discussed with this as another example of how this property blurs the lines between CSS and HTML.
  • Discussion will return to github with examples added to hopefully make the issue less abstract.
• Resolved: line-clamp: integer with a height constraint clamps by height or by lines, depending on what comes earlier, pending compat issues (Issue #12041: Can you line-clamp by both a number of lines and a height at the same time?)

Full Meeting Minutes

By Dael Jackson September 3, 2025 (Permalink)
Categories: resolutions

• Resolved: Publish CSS 2025 as a Note once all edits from this meeting are in (Issue #12715: Publish Snapshot as Group Note)
• Resolved: Move cascade-5 to the Reliable CR section (Issue #12702: Add CSS Cascade 5 to Reliable CRs)
• Resolved: Move css-color-adjust-1 to Reliable CR section (Issue #12692: Add CSS Color Adjust 1 to Reliable CRs)
• Resolved: css-conditional-4 to Reliable CR section (Issue #12694: Add CSS Conditional 4 to Reliable CRs)
• Resolved: Close, no change (Issue #12697: Add CSS Shapes 1 to Reliable CRs)
• The group will come back to issue #12691 (Add CSS Will Change 1 to Reliable CRs) after folks have had a chance to review the current open issues list.
• Resolved: Close, no change (Issue #12712: Add Media Queries 5 to Rough Interop)
• Resolved: Publish new WD of css-nesting (Issue #12704: Add CSS Nesting 1 to Rough Interop)
• Prior to resolving on issue #12711 (Add CSSOM View 1 to Rough Interop) republishing CSSOM View will be brought to the wider group.
• CSS Overscroll needs an active editor before the group can decide on issue #12701 (Add CSS Overscroll 1 to Rough Interop).

Full Meeting Minutes

By Dael Jackson August 13, 2025 (Permalink)
Categories: resolutions

• Resolved: Use :interest-source and :interest-target (Issue #12515: Suggest a better name for the `:interest-target` pseudo class)
• There were concerns about the proposal for issue #12040 (`getClientRects()` should return a flattened list of child rects for `display: contents`) limiting anchor positioning or parts users so discussion will return to github.
• Resolved: Define that subgrid repeat works exactly the same as grid repeat (Issue #8493: Subgrid auto repeat calculation when `line-name-list` size isn’t a multiple of remaining subgrid tracks)
• Resolved: Create level 2 diff spec for anchor pos and define an anchored keyword for container-type there (Issue #12390: Add a new container-type `anchored` for querying anchored elements)
• Resolved: Define a fallback container feature used in the anchored query function (Issue #12391: Add a `fallback` feature for querying applied fallback for anchored elements)
• Resolved: Add three methods to AnimationTrigger interface: addAnimation, removeAnimation and getAnimations (Issue #12397: How do AnimationTriggers attach to animations?)

Full Meeting Minutes

By Dael Jackson August 7, 2025 (Permalink)
Categories: resolutions

• Resolved: Republish Color Adjust
• Resolved: Pursue this functionality in HTML. Close this issue. (Issue #12437: Add a `::interest-hint` pseudo element to interest invokers)
• Resolved: All percentages (insets, sizes) resolve against the effective containing block (no inconsistency) (Issue #10861: Introduce “document containing block” for some purposes?)
• The solution for issue #12371 (Define precisely when anchor recalc points happen, and which offsets it captures) is potentially editorial and needs to be investigated a bit further. Directionally, the proposal is anchor positioned boxes recalculate layout for all changes that might affect their size/position except scrolling except for special recalculation points.
• Resolved: Make Animation Trigger related things readonly (Issue #11918: Should AnimationTrigger properties be readonly?)
• Resolved: Adopt syntax ‘columns: [ column-width || column-count ] [ / column-height ]? (Issue #12050: `columns` shorthand with `column-height` and `column-wrap`)
• Resolved: Shorthand ‘columns’ also resets column-wrap (if it exists) (Issue #12050)
• Resolved: Don’t use env() for this. Use an @page descriptor roughly as proposed by dholbert; work out details in the issue. (Issue #11395: Expose unprintable areas via CSS)
• Resolved: Accept Elika’s bullet points in the last comment (Issue #8842: Float and first-letter pseudo-element interaction missing from the latest specs)

Full Meeting Minutes

By Dael Jackson August 6, 2025 (Permalink)
Categories: resolutions

• Resolved: Change name to rule-overlap (Issue #12540: Bikeshedding rule-paint-order)
• Resolved: Update definition of gap with gutter terminology (Issue #12084: Gap intersection point definition might need updating for multi-col)
• Resolved: Apply all decorations from left to right (Issue #12527: Values after an auto repeater when there’s fewer values than gaps)
• Resolved: Define gap decoration animations using LCM methods (Issue #12431: Define interpolation behavior)
• astearns will tag additional folks in issue #12201 (Serializing `column-rule` shorthand from separate longhands) to get those with expertise in shorthands to weigh in.

Full Meeting Minutes

By Dael Jackson July 30, 2025 (Permalink)
Categories: resolutions

• Resolved: Add CSS URL to “Safe to Release pre-CR Exceptions” of 2025 Snapshot. (Issue #12539: Add CSS URL modifiers to the 2025 snapshot)
• Before deciding on issue #12482 (Add CSS `random()` function to the 2025 Snapshot) the group will get wide review on random().
• Resolved: If multiple values are omittable in serialization, but at least one is required, choose the first one in grammar order unless constrained by compat. (Issue #12486: Clarify expected computed value for `text-decoration` and similar shorthands (can we omit resolved `currentColor`?))
• Resolved: If a `color` value is omittable when computed to currentColor, then it is omittable even though the resolved value is not the ‘currentColor’ keyword (because colors are absolutized), unless constrained by compat. (Issue #12486)
• Resolved: When only one auto inset, ‘normal’ alignment with position-area resolves to the alignment that attaches to the non-auto edge. (Issue #12512: More intuitive alignment defaults when using one-sided insets)
• There was broad agreement that the current behavior mentioned in issue #10258 (Handling popover default styles) was confusing and needed to be fixed. There are concerns that the proposal may not be compatible and may make styling difficult. Discussion will return to github to investigate further.

Full Meeting Minutes

By Dael Jackson July 16, 2025 (Permalink)
Categories: resolutions

• There were no concerns about the resolution on issue #9740 (`&` matching inside the `@scope`, and its interaction with `:scope`) from the breakout.
• Resolved: appearance: base-select can be used to opt listbox selects into base appearance. control of listbox and multiple rendering will be improved in html (Issue #12468: Should `appearance: base-select` work on listbox selects? (`select size`/`select multiple`))
• Next steps for issue #10372 (Mitigating fingerprinting for AccentColor/AccentColorText) is to discuss the magnitude of the fingerprinting concern with security and privacy teams and then move on to creating draft text.
• Resolved: when caret is past the end of the line, attempt to show it even if it overflows. Browser may clip it or reposition it (Issue #10289: caret-shape: block/underscore and overflow)
• Resolved: compute missing content-visibility information as we iterate the tree while capturing (Issue #10773: Elements with content-visibility in new Document)
• Resolved: Add / delimiter to syntax for animation-trigger (Issue #11948: Add / separator before animation-trigger exit range)
• There were several concerns raised about the design of the solution for issue #12336 (Move scroll and event animation triggers to independent namespace) and so discussion will return to github.

Full Meeting Minutes

By Dael Jackson July 9, 2025 (Permalink)
Categories: resolutions

• Resolved: Close, no change (Issue #11711: Alternative proposal for `dynamic-range-limit` defaults)
• Resolved: Move the rendering details of legend, fieldset, button and appearance from HTML spec to CSS Forms (Issue #10039: Styling of native appearance)
• Resolved: No longer pursue pem units. Adopt proposed meta for opting into adjustable text scale. (Issue #12380: New `meta text-scale` tag to make UA initial font size respond to OS text scale setting)
• Resolved: Add env() function to @supports (Issue #3576: Need an approach to check whether an environment variable is supported)

Full Meeting Minutes

By Dael Jackson July 3, 2025 (Permalink)
Categories: resolutions

• Pseudo classes for the `interestfor` API (Issue #12154):
  • Concerns were raised that `possible` my be cyclic; if it causes issue it may be dropped.
  • There was no clear agreement on how `partial` will work, especially in a mobile context. Discussion will continue on github and `partial` will move to a separate issue to make discussions easier.
• Resolved: Publish css-borders-4 with the edits described [add an introduction and move the not ready for implementation to partial borders]
• Resolved: Allow shipping with no-autospace as initial value, continue discussing eventual default behavior (Issue #12386: Reconsider the initial value of the `text-autospace` property)
• Resolved: Republish the WD (Issue #6245)
• There were several concerns raised on issue #12132 (Using logical keywords in background-position shorthand with multiple backgrounds) around how to implement and how to cascade. There wasn’t time to dive in further during the call so group members were asked to add examples of how the concerns would manifest to the github issue.

Full Meeting Minutes

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4