Minutes OpenUI-WHATWG/HTML-CSSWG Joint Meeting 2024-11-21
OpenUI-WHATWG/HTML-CSSWG meeting
Selectors
- The group agreed to remove :closed for now and keep :open (Issue #11039: Should we have :open and :closed?)
CSS UI
- Resolved: Use currentColor for borders, inherit the color, transparent background color (for in-page controls). Use system colors for pickers (Issue #10909: Colors to use for appearance:base `select`)
- jahrar presented slides for issue #10857 (UA stylesheet for appearance:base `select`) and requested feedback and questions in github.
Full Meeting Minutes
Minutes Telecon 2024-11-20
- Resolved: Name the pseudo-element ::checkmark (Issue #10908: Pseudo-elements for checkmark and dropdown icon for appearance:base `select`)
- Resolved: Go with ::picker-icon (Issue #10908)
- noamr introduced the proposal to remove ‘auto’ (Issue #10995: Allow an auto-generated `view-transition-name` that doesn’t default to ID). There were objections to the removal so discussion will return to github.
- Resolved: Close no change (Issue #11097: Should forced-colors support `color-mix()`?)
- Resolved: Rename “overflowing” to “scrollable” (Issue #11182: scroll-state(overflowing) is confusing because it ignores clipped overflowing content)
Full Meeting Minutes
Minutes Overflow Breakout 2024-11-20
- Resolved: Go with option 2 and make them siblings (Issue #11125: Tree structure of scroll container controls)
- Resolved: Choose option 2 [Before Markers, Buttons, Content, After Markers] in the issue (Issue #10912: Focus order of generated controls)
- Resolved: Adopt proposal to anchor to identified elements (Issue #10738: Allowing markers to be active even when not scrollable to aligned position)
- Resolved: Use :target-current for the name (Issue #10918: Bikeshed pseudoclasses for active scroll-marker)
- Resolved: Accept flackr’s proposal in the issue (Issue #11216: Disabled scroll-button state and styling)
- Resolved: Go with Option 5 [Distribute some amount of the initial and ending scroll] (Issue #11165: Scrolling to unreachable scroll aligned marker positions)
- Resolved: Publish Overflow 5 as FPWD
Full Meeting Minutes
Minutes Telecon 2024-11-13
- Resolved: Publish new WD of View Transitions 2
- Resolved: Republish Pseudo 4, move glazman to former editor
- Resolved: Publish new WD of Nesting
- Resolved: Add new category, shorthanded as “reliable CR” (Issue #9770: Add specs to Official Definition)
- Resolved: Add Media Queries 4 and Scroll Snap to “reliable CR” (Issue #9770)
- Resolved: Move Grid 1 and Grid 2 to “reliable CR” (Issue #9770)
- Spec editors are asked to post their opinions of where those specs should be placed in the snapshot so that the group can do a bulk set of resolutions in the near future.
- Resolved: Accept proposal to use type(`syntax`), add string, and add units as keywords (Issue #11035: attr() and forwards compatible parsing)
- Resolved: Accept the changes to the shape() grammar (Issue #10649: `curve to` keyword `using` seems a bit off)
- Resolved: Using ‘border-area’ in the background shorthand (and omitting origin) defaults the origin to border-box (Issue #11167: Default background-origin for `border-area` in shorthand)
Full Meeting Minutes
Updates to CSS Values and Units Level 5
The CSS Working Group has published an updated Working Draft of CSS Values and Units Module Level 5. This module defines CSS’s value types and functions, as well as our value definition syntax, and is currently drafted as a diff spec over CSS Values and Units Level 4.
This update adds if(), inherit(), a redesigned attr(), and a new multiplier notation <boolean-expr[]> for the value definition syntax. Changes since the last Working Draft are listed in the Changes section.
This draft is not very stable, as the features are in an exploratory design phase, and may change significantly in response to feedback. Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list [email protected] with the spec code ([css-values-5]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Open UI-WHATWG/HTML-CSSWG meeting 2024-11-07
OpenUI-WHATWG/HTML-CSSWG meeting
CSS UI
- The group began the discussion of proposed properties for the UA stylesheet (Issue #10587: UA stylesheet for appearance:base `select`) with padding:0.25em.
- The group liked having the value in em, though there wasn’t clear consensus if 0.25em was right.
- It was stressed that in creating this we should keep in mind good accessibility and user expectations and not be tied to existing behavior.
- It’s also likely authors will overwrite this, so keeping it lightweight.
- The styling depends on content which is a new pattern and may require thought to the naming to avoid author confusion.
- The group discussed using currentColor vs system color for the picker in issue #10909 (Colors to use for appearance:base `select`)
- The group tried to figure out what would be the most expected for developers and the most minimal since they expect it to be overwritten.
- Right before the call concluded, they also started exploring how to ensure that there is appropriate contrast.
Full Meeting Minutes
Minutes Telecon 2024-11-06
- Resolved: Add `boolean-expr[…]` as a value definition syntax function multiplying its argument into a boolean expression microsyntax (Issue #10457: `condition` type that other specs reference)
- Resolved: Publish a new WD of Values 5
- Resolved: Change Animation.progress to Animation.overallProgress (Issue #8799: Progress APIs)
- Resolved: Close no change (Issue #10706: How are invalid types validated?)
- Resolved: Add `border-area || text` to the background-clip syntax (Issue #10696: Can you chain `border-area` and `text` in `background-clip`?)
Full Meeting Minutes
Minutes Telecon 2024-10-30
- Resolved: Accept the PR (Issue #10271: Add interpolation between multiple values of dynamic-range-limit)
- smfr will research if webkit is able to change to the chromium behavior for issue #4165 (Should CSS decorative images respect EXIF-orientation by default) which the group will use to guide the resolution.
- Resolved: Change the spec to match reality around child-of-root BODY elements (Issue #10549: Spec for offsetTop/Left does not match impls when offsetParent is `position:static` `body` element)
- Resolved: Plain text copy must ignore text replaced autospace. open to other feedback (Issue #8511: text-autospace: what gets copied?)
- Comments are requested in issue #3434 (Prevent line breaking after explicit hyphens) to help move the conversation toward a resolution.
Full Meeting Minutes
Minutes View Transitions Breakout 2024-10-30
- The below resolutions will be confirmed with the rest of the working group asynchronously due to light attendance.
- Resolved: `auto` will match elements using their ID attributes, falling back to element identity; `match-element` will only use element identity (Issue #10995: Allow an auto-generated `view-transition-name` that doesn’t default to ID)
- Resolved: We will use `match-element` in the Animations API when element identity is used (Issue #10978: How are auto-generated `view-transition-name`s exposed in JS APIs)
- noamr created an explainer for issue #10585 (Optionally capture some properties (e.g. opacity/border) as style instead of snapshot). There were some initial questions on if both modes should exist. Folks will read the explainer and discuss further.
Full Meeting Minutes
OpenUI-WHATWG/HTML-CSSWG meeting 2024-10-23
OpenUI-WHATWG/HTML-CSSWG meeting
CSS UI
- Resolved: Add pseudo-elements for the select button and option checkmarks which are fully stylable pseudo-elements with content specified by the content property (Issue #10908: Pseudo-elements for checkmark and dropdown icon for appearance:base select)
- Resolved: Adopt ::check or ::checkmark for checkbox/radio checks (Issue #10908)
- jarhar will open an issue to determine if pseudo elements (yet to be named) are tree-like or element-like.
- The group reviewed the potential implementation of the proposal for issue #10909. There was concerns that border being currentColor was both non-intuitive for developers and going to cause additional work to change. There was discussion around the pros and cons of using system colors which would make something predictable, but also may cause issues for things like high contrast mode. Discussion will return to github.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: