Re: [csswg-drafts] [css-ui-3] Check edits since publication as REC (#13019)

Among a bunch of commits, I found the following ones to be notable:

1a57a4025 is an extensive edit intended to be editorial, but which did introduce some text redundancy ([fixed](https://github.com/w3c/csswg-drafts/commit/d53db3c9b220d30d7ac91b82029cf6bbd49c2c00)), and [one bug](https://github.com/w3c/csswg-drafts/issues/13001) ([fixed](https://github.com/w3c/csswg-drafts/pull/13018)).

8f5f6832b doesn't seem like it's editorial, and I'm not sure we have a resolution for it. Clarity on what happens with `overflow: clip` is desirable, so I suggest we review these edits and decide whether to keep them. Specifically:
*  ```diff
   Name: resize
   Value: none | both | horizontal | vertical
   Initial: none
   -Applies to: elements with 'overflow' other than visible,
   +Applies to: elements that are <a>scroll containers</a>
    ```
   and
   ```diff
   The 'resize' property applies to elements
   whose computed 'overflow' value
   -is something other than ''visible''.
   +that are <a>scroll containers</a>.
   ```
     This matches what Chrome and Firefox do, but not what Safari does, which does make `resize` apply to elements with `overflow: clip`. [test](https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=14271)

* ```diff
   Name: text-overflow
   […]
   This property specifies rendering when inline content overflows
   its <a>end</a> line box edge
   in the inline progression direction of its block container element ("the block")
   that has 'overflow'
   other than ''visible''.
  +<!-- REVIEW: I *think* this should not include ''overflow/clip'' -->
   ```
   Despite what the comment says, all 3 browsers do conform to the spec, and also ellipsize in the case of `overflow: clip`. [test](https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=14272).

29b1dae509aa2e2690b8f8a36810e0bc4a0bc246 seems like a useful clarification, but I could not find a specific resolution to apply it to the `outline` property (https://github.com/w3c/csswg-drafts/issues/5210 does have a resolution to introduce the concept, but not where to apply it to). We probably should pass one. Since this is only a refinement, we might want to keep it to level 4 only, but then again, it does seem to pass [a corresponding test](https://wpt.fyi/results/css/css-ui/outline-width-rounding.tentative.html?label=master&label=experimental&aligned&q=%2Fcss%2Fcss-ui%2Foutline-width-rounding.tentative.html) in all browsers, so maybe we can keep it in both.

Based on the above, agenda+ to propose:
* Doubling down on `text-overflow` applying for all non-`visible` values of `overflow`, not just those that cause the element to become a scroll container.
* Deciding whether to side with Firefox/Chrome or Safari on `resize` applying or not to elements with `overflow: clip`
* Resolving that `outline-width`'s computed value as a length should be "snapped as a border width"

Once we've done all that, we may want to consider publishing an updated version of CSS-UI-3, with the editorial changes folded in, and the normative ones marked as proposed corrections.




-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13019#issuecomment-3454148057 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 28 October 2025 02:14:43 UTC