commit | a687e1c3da8c5ff8968776d5b72d370d019dc552 | [log] [tgz] |
---|---|---|
author | David Baron <dbaron@chromium.org> | Mon Apr 14 23:02:39 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 14 23:02:39 2025 |
tree | 10af7e96f9f2679d27952f8b554c94567ce8ee33 | |
parent | 00b63a3e5a3fa6b9992f456740e261366131f6ad [diff] |
Make resizing relative to original position. When resizing an element with the CSS resize property such as a textarea, changing the size of the element might move the origin (top-left corner) of the element. This makes such changes not affect what a resize gesture is relative to, by storing the transform at the start of a resize. This makes resizing of elements that are positioned relative to the end-edge of the layout, or centered, etc. work better. (The existing code worked properly for start-edge positioned elements in both LTR and RTL.) This operates on the principle that the desired size change (visible, after transforms) is the amount of mouse movement, and it's ok if that means the mouse is no longer tracking the position of the resizer. Prior to the change, these two added tests fail: external/wpt/css/css-ui/resize-textarea-relative-to-right-001.tentative.html external/wpt/css/css-ui/resize-textarea-rtl-002.tentative.html Note that existing web tests test resizers with transforms: fast/css/resize-corner-tracking-transformed-iframe.html fast/css/resize-corner-tracking-transformed.html external/wpt/css/css-overflow/resizer-transform.tentative.html Fixed: 40697767, 41236895 Change-Id: I31382aa84af4d4836fba54e8af4622213a320d3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6441001 Commit-Queue: David Baron <dbaron@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/main@{#1446823}
Chromium 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.