[css-ui-3] Check edits since publication as REC

[frivoal]

There have been edits made to css-ui-3 since its publication as REC made by people other than the listed editors, some without WG resolution, some editorial, some normative, including some which were mistakes (see for example #13001).

This is an issue to remind myself to look into the history, review the edits, and bring back to the group anything that needs confirmation.

[frivoal]

Note to self: WIP, checked up to and including 2a26846.

[SebastianZ]

@frivoal FYI, I am currently adding WPTs to different specs. And CSS UI 3 and 4 are currently missing them.

So if the plan is to publish a revised version of the recommendation, maybe we could include the WPTs.

Sebastian

[frivoal]

@SebastianZ keeping in mind that some of css-ui-4 is on its way to css-forms-1, that sounds like a good idea if you can take the time. In any case, css-ui-3 is stable, so you should not be worried about moving targets as far as it's concerned.

[SebastianZ]

I've added WPTs to both levels in #13026. @frivoal Would be great if you could review the PR.

Sebastian

[frivoal]

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

1a57a40 is an extensive edit intended to be editorial, but which did introduce some text redundancy (fixed), and one bug (fixed).

8f5f683 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:

• 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

  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

•  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.

29b1dae seems like a useful clarification, but I could not find a specific resolution to apply it to the outline property (#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 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.