Fix a crash by search event handler for <input type=search incremental>.

Fix a crash by search event handler for <input type=search incremental>.

We had a crash in SearchInputType::didSetValueByUserEdit().

Dispatching a synchronous event here is dangerous. This CL makes the
non-standard 'search' event dispatching asynchronous in the following cases:
 - The input value becomes empty.
 - The form is submitted implicitly.
Basically 'search' event is triggered by input value changes, and is dispatched
asynchronously by a timer.  So, the behavior change should be acceptable.

BUG=570427
TEST=automated

Committed: https://crrev.com/dd6acb021e38e8181684026899fdef556099e408
Cr-Commit-Position: refs/heads/master@{#365773}

[tkent, 2015-12-17 03:30:45]

The CQ bit was checked by tkent@chromium.org to run a CQ dry run

[tkent, 2015-12-17 03:30:51]

Patchset #1 (id:1) has been deleted

[tkent, 2015-12-17 03:30:56]

Patchset #1 (id:20001) has been deleted

[tkent, 2015-12-17 03:31:01]

Patchset #1 (id:40001) has been deleted

[tkent, 2015-12-17 03:31:39]

Description was changed from

==========
Fix a crash by search event handler for <input type=search incremental>.

We had a crash in SearchInputType::didSetValueByUserEdit().

Dispatching a synchronous event here is dangerous. This CL makes the
non-standard 'search' event dispaching in the following cases asynchronous.
 - The input value becomes empty.
 - The form is submitted implicitly.
Basically 'search' event is triggered by input value changes, and is dispatched
asynchronously by a timer.  So, the behavior change should be acceptable.

BUG=570427
TEST=automated
==========

to

==========
Fix a crash by search event handler for <input type=search incremental>.

We had a crash in SearchInputType::didSetValueByUserEdit().

Dispatching a synchronous event here is dangerous. This CL makes the
non-standard 'search' event dispatching asynchronous in the following cases:
 - The input value becomes empty.
 - The form is submitted implicitly.
Basically 'search' event is triggered by input value changes, and is dispatched
asynchronously by a timer.  So, the behavior change should be acceptable.

BUG=570427
TEST=automated
==========

[commit-bot: I haz the power, 2015-12-17 03:34:43]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1529373002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1529373002/60001

[commit-bot: I haz the power, 2015-12-17 05:21:59]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-12-17 05:22:00]

Dry run: This issue passed the CQ dry run.

[tkent, 2015-12-17 05:28:50]

tkent@chromium.org changed reviewers:
+ kochi@chromium.org

[tkent, 2015-12-17 05:28:51]

kochi@, would you review this please?

A typical fix for this kind of crashes is to make the event scoped, and add
EventQueueScopes to problematic code paths.  However, I didn't take that way
because there are too many afected code paths.

[kochi, 2015-12-17 07:21:46]

lgtm

[tkent, 2015-12-17 07:23:05]

The CQ bit was checked by tkent@chromium.org

[commit-bot: I haz the power, 2015-12-17 07:24:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1529373002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1529373002/60001

[commit-bot: I haz the power, 2015-12-17 07:30:23]

Committed patchset #1 (id:60001)

[commit-bot: I haz the power, 2015-12-17 07:31:23]

Description was changed from

==========
Fix a crash by search event handler for <input type=search incremental>.

We had a crash in SearchInputType::didSetValueByUserEdit().

Dispatching a synchronous event here is dangerous. This CL makes the
non-standard 'search' event dispatching asynchronous in the following cases:
 - The input value becomes empty.
 - The form is submitted implicitly.
Basically 'search' event is triggered by input value changes, and is dispatched
asynchronously by a timer.  So, the behavior change should be acceptable.

BUG=570427
TEST=automated
==========

to

==========
Fix a crash by search event handler for <input type=search incremental>.

We had a crash in SearchInputType::didSetValueByUserEdit().

Dispatching a synchronous event here is dangerous. This CL makes the
non-standard 'search' event dispatching asynchronous in the following cases:
 - The input value becomes empty.
 - The form is submitted implicitly.
Basically 'search' event is triggered by input value changes, and is dispatched
asynchronously by a timer.  So, the behavior change should be acceptable.

BUG=570427
TEST=automated

Committed: https://crrev.com/dd6acb021e38e8181684026899fdef556099e408
Cr-Commit-Position: refs/heads/master@{#365773}
==========

[commit-bot: I haz the power, 2015-12-17 07:31:23]

Patchset 1 (id:??) landed as
https://crrev.com/dd6acb021e38e8181684026899fdef556099e408
Cr-Commit-Position: refs/heads/master@{#365773}