commit | 71263453249c02fb8d4779c579afc5392a2d3496 | [log] [tgz] |
---|---|---|
author | Nick Diego Yamane <nickdiego@igalia.com> | Thu Jan 14 23:21:28 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 14 23:21:28 2021 |
tree | a189dc0a1e560a84a6b2744d34f5bde32cd33cb8 | |
parent | 38a8cb1db88c371899967130ddaaabfbbace0ae0 [diff] |
tabdrag: Fix tabstrip layout when dragging out of a maximized window When a tab is dragged out of a maximized window, the detached window is created in restored state (ie: with different geometry) and tab drag controller needs to adjust the window and dragged tabs' bounds (more specifically x location), so that they appear under the pointer. That's done at TabStrip::TabDragContextImpl::SetBoundsForDrag() function [2], which calls into Views::SetBoundsRect() for each selected Tab view. It turns out that it is not enough to ensure the tabstrip and its parent, TabStripRegionView, get properly re-laid out, leading to issues like [1], where the dragged tab gets partially or totally occluded by the TabStripRegionView's child views. To fix it, this CL adds layout invalidation for tab strip just after setting bounds rect for each dragged tabs, ensuring both tab strip and its parent views are correctly relaid out. Bug: 1151092 [1] https://drive.google.com/file/d/1a6kEVy0DNUo9TTeiCYjkpf7d42TI3T7n [2] https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/views/tabs/tab_strip.cc;l=697-708;drc=d81c5852498699fe3cd812e78d31c77c28e29281 R=sky@chromium.org Change-Id: I51244ad4485856334ce3443ed92ce80e2fad2cd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572040 Commit-Queue: Nick Yamane <nickdiego@igalia.com> Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by: Taylor Bergquist <tbergquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#843781}
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.