Bogus 'search-changed' event fired from CrSearchFieldBehavior on startup. |
||
Issue descriptioncr_search_field_behavior is firing an accidental 'search-changed' event on startup even though the user did not issue any search (because of how Polymer property observers work). Working around this makes client code cryptic (and puzzles reviewers). I have a fix and a test at https://codereview.chromium.org/2458113003.
,
Oct 28 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Oct 28 2016