| commit | af046fa668e1fe8f7de1ef249fb4579706d0e10a | [log] [tgz] |
|---|---|---|
| author | Mason Freed <masonf@chromium.org> | Tue Aug 06 16:49:37 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 06 16:49:37 2024 |
| tree | a5cebb0688868eb37b7c8f9f6bce2b7ee41adcd3 | |
| parent | 222a344f0d747d907eb34497adb7ed73663fc384 [diff] |
Rename inset-area to position-area Per the CSSWG, this property has been renamed: https://github.com/w3c/csswg-drafts/issues/10209#issuecomment-2221005001 This does a mechanical rename: - `inset-area` to `position-area` - `insetArea` to `positionArea` - `InsetArea` to `PositionArea` - `inset_area` to `position_Area` After the mechanical rename, there were a handful of hand-fixups, e.g. in cases where the old property (inset-area) needs to stay, or in setting up feature access to both. This CL also adds a surrogate from `inset-area` to `position-area`, so that both names keep working. Separate runtime flags are created to enable either of these property names. As-is, `inset-area` is enabled for "stable", and `position-area` is "experimental". And finally, a virtual test suite is added that enables `inset-area` and disables `position-area` and tests that the old WPTs still pass. Note that the WPTs had to be slightly modified for their new copied location within the VTS. Bug: 352333393 Change-Id: I92d3347ae109546a155771a21b5d6aee2a81391d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5698212 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1337930}
ChromiumChromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.
