forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
WebUI: cr-search-field-behavior, update value with potentially no eve…
…nt first When there is a search term present, navigating to another section or about page cleared the search term. The |setValue()| is being called with an argument that should avoid firing a 'search-changed' event. Due to the order of how the values are updated, |setValue()| could be called more than once due to a single |setValue()| call. The subsequent calls to |setValue()| can potentially fire a 'search-changed' event if the search value has changed. It is therefore important to update the underlying search term and last value first while respecting the no event argument. Once completed, the remaining logic can be executed. Bug: 954457 Change-Id: I3d4ce6933ba04419b529f45eeeb8ba2ed4977687 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585174 Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#655665}
- Loading branch information
Esmael El-Moslimany
authored and
Commit Bot
committed
May 1, 2019
1 parent
642e725
commit ab146f9
Showing
2 changed files
with
50 additions
and
21 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