-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[AppList] Fix positioning of close button when using search box
When activating the search box in tablet mode, the close button can sometimes end up positioned incorrectly because the close button is laid out next to the assistant button during the fade in/out animations. To fix this, put the assistant button and the close+filter buttons inside their own container views. These container views are then parented by a fill layout manager view, so that the button containers overlap are laid out on top of each other instead of side by side. This makes it so that the button fade in/out animations overlap correctly. Also, to simplify the fade in/out animations, animate the opacity of the button containers instead of the buttons themselves. This also allows button press events to pass to the correct button once the overlapping containers are set to !visible after the fade out animations complete. Finally increment pixel test revisions, and simplify some of the numbering by skipping a revision for the case when IsJellyEnabled() is false. Some revisions also had to be skipped because these pixel tests were incremented previously but the change was reverted. This simplification should make these revision changes easier to deal with moving forward. Bug: b/302376415 Change-Id: I820ecd3ece99736d69172b2e3a15171117f95bc8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4914639 Commit-Queue: Matthew Mourgos <mmourgos@chromium.org> Reviewed-by: Wen-Chien Wang <wcwang@chromium.org> Cr-Commit-Position: refs/heads/main@{#1211916}
- Loading branch information
Matthew Mourgos
authored and
Chromium LUCI CQ
committed
Oct 19, 2023
1 parent
0ad87e6
commit e14a104
Showing
7 changed files
with
124 additions
and
95 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.