Skip to content

Conversation

@cdoublev
Copy link
Collaborator

@cdoublev cdoublev commented Sep 5, 2025

Fix oversights in f3d0da1.

corners is basically renamed to corner:

Thanks. So I guess corners is now corner. So is there any reason to keep 3.4. Corner Shaping Shorthand: the corners property?

Oh I thought I removed the leftover. No there isn't.

#11623 (comment)

@cdoublev cdoublev requested a review from noamr September 5, 2025 13:40
@SebastianZ
Copy link
Contributor

"Additions since [[CSS3BG]]" still mentions corners. That should also be changed to corner.

Sebastian

@cdoublev
Copy link
Collaborator Author

cdoublev commented Sep 6, 2025

This PR also adds the item "renamed corners to corner" (resolution) to the "latest changes" section. So I should remove this item; you do not want to keep track of this, and just pretend that corner was originally added, right?

@SebastianZ
Copy link
Contributor

This PR also adds the item "renamed corners to corner" (resolution) to the "latest changes" section. So I should remove this item; you do not want to keep track of this, and just pretend that corner was originally added, right?

The rename should still be mentioned in the "Changes since the First Public Working Draft of 22 July 2025" section, as in the FPWD it is still named corners.

Though the "Additions since [CSS3BG]" section should only mention corner, i.e. it should read like this:

added corner-shape and corner-*-shape shorthands plus related corner and corner-* shorthands

Sebastian

@cdoublev
Copy link
Collaborator Author

cdoublev commented Sep 6, 2025

I get it. The two lists do not define changes that occurred during two successive intervals. Done.

@SebastianZ
Copy link
Contributor

Great! Thanks, @cdoublev!

@SebastianZ SebastianZ merged commit ec0651c into w3c:main Sep 6, 2025
1 check passed
@cdoublev cdoublev deleted the patch-2 branch September 6, 2025 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants