[css-gaps-1] Update outset properties #12603, #12848, #8402#13024
Merged
Conversation
Contributor
|
See the comments in #12603 (comment). Sebastian |
Collaborator
|
See also #12848 (comment). |
added 3 commits
November 3, 2025 08:26
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Nov 10, 2025
Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this will require some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Nov 10, 2025
Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251
philwo
pushed a commit
to philwo/chromium
that referenced
this pull request
Nov 10, 2025
Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7127743 Commit-Queue: Javier Contreras <javiercon@microsoft.com> Reviewed-by: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1542664}
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Nov 10, 2025
Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7127743 Commit-Queue: Javier Contreras <javiercon@microsoft.com> Reviewed-by: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1542664}
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Nov 10, 2025
Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7127743 Commit-Queue: Javier Contreras <javiercon@microsoft.com> Reviewed-by: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1542664}
lando-worker Bot
pushed a commit
to mozilla-firefox/firefox
that referenced
this pull request
Nov 11, 2025
…ties to `inset`, a=testonly Automatic update from web-platform-tests [gap-decorations] Rename `outset` properties to `inset` Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7127743 Commit-Queue: Javier Contreras <javiercon@microsoft.com> Reviewed-by: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1542664} -- wpt-commits: b309d20b304af67e4c7e38c5ebd220a47347edb9 wpt-pr: 55960
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this pull request
Nov 12, 2025
…ties to `inset`, a=testonly Automatic update from web-platform-tests [gap-decorations] Rename `outset` properties to `inset` Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7127743 Commit-Queue: Javier Contreras <javierconmicrosoft.com> Reviewed-by: Alison Maher <almahermicrosoft.com> Cr-Commit-Position: refs/heads/main{#1542664} -- wpt-commits: b309d20b304af67e4c7e38c5ebd220a47347edb9 wpt-pr: 55960 UltraBlame original commit: 4fa50156d3f62d236b76cd3539c506796445628e
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this pull request
Nov 13, 2025
…ties to `inset`, a=testonly Automatic update from web-platform-tests [gap-decorations] Rename `outset` properties to `inset` Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7127743 Commit-Queue: Javier Contreras <javierconmicrosoft.com> Reviewed-by: Alison Maher <almahermicrosoft.com> Cr-Commit-Position: refs/heads/main{#1542664} -- wpt-commits: b309d20b304af67e4c7e38c5ebd220a47347edb9 wpt-pr: 55960 UltraBlame original commit: 4fa50156d3f62d236b76cd3539c506796445628e
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this pull request
Nov 13, 2025
…ties to `inset`, a=testonly Automatic update from web-platform-tests [gap-decorations] Rename `outset` properties to `inset` Per recent resolutions to the spec, rule `outset` properties are going to be named with `inset` instead. Although this requires some changes in behavior, this CL only renames the relevant properties (and their shorthands). A follow up CL will rename any test files referring to "outset" and a follow up CL to that will implement the change in behavior along with the changes in tests. w3c/csswg-drafts#12848 w3c/csswg-drafts#12603 The links in some comments have been modified too to point to their new sections in the spec, although they won't work right now since the PR to change the spec is still under review w3c/csswg-drafts#13024. Bug: 357648037, 440054556 Change-Id: I81414a8dc7ee9974e90dbae38f46ee85d76a6251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7127743 Commit-Queue: Javier Contreras <javierconmicrosoft.com> Reviewed-by: Alison Maher <almahermicrosoft.com> Cr-Commit-Position: refs/heads/main{#1542664} -- wpt-commits: b309d20b304af67e4c7e38c5ebd220a47347edb9 wpt-pr: 55960 UltraBlame original commit: 4fa50156d3f62d236b76cd3539c506796445628e
kbabbitt
reviewed
Dec 15, 2025
outset properties #12603outset properties #12603, #12848, #8402
kbabbitt
approved these changes
Dec 17, 2025
kbabbitt
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for writing this up! I pushed one more commit, only because I wanted to reorder a couple of points for reading flow and it was easier to make the changes than to explain them in inline comments.
Collaborator
|
Just remembered one other thing: Could you add a line to the Changes section? |
yisibl
reviewed
Dec 17, 2025
added 2 commits
December 17, 2025 09:26
…-gaps-1 into asymmetric-outsets
kbabbitt
approved these changes
Dec 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://jav099.github.io/javier-intersections-draft.github.io/