DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context menu state on Mac

DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556
Committed: https://crrev.com/b231468fd5825415fff761c25f561c8c782ab25c
Cr-Commit-Position: refs/heads/master@{#429498}

[luoe, 2016-11-02 21:09:53]

Description was changed from

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state

BUG=655556
==========

to

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556
==========

[luoe, 2016-11-02 21:10:29]

Description was changed from

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556
==========

to

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556
==========

[luoe, 2016-11-02 21:10:42]

luoe@chromium.org changed reviewers:
+ dgozman@chromium.org

[dgozman, 2016-11-02 23:04:00]

lgtm

[luoe, 2016-11-02 23:28:00]

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

[commit-bot: I haz the power, 2016-11-02 23:28:52]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-03 01:10:04]

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

[commit-bot: I haz the power, 2016-11-03 01:10:05]

Dry run: This issue passed the CQ dry run.

[luoe, 2016-11-03 01:10:27]

The CQ bit was checked by luoe@chromium.org

[commit-bot: I haz the power, 2016-11-03 01:11:12]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-03 01:16:13]

Description was changed from

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556
==========

to

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556
==========

[commit-bot: I haz the power, 2016-11-03 01:16:14]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-11-03 01:18:24]

Description was changed from

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556
==========

to

==========
DevTools: throttle calls to ToolbarMenuButton.trigger() to avoid bad context
menu state on Mac

WI.ToolbarMenuButton shows a real (not-soft) contextMenu on click. It is
possible to reach a bad state on Mac OS by focusing on a different window, then
making two fast clicks on a ToolbarMenuButton (e.g. 3 dot drawer menu) in the
originally unfocused DevTools. On the first mouse press, nothing happens, but on
the second, two mousedown events are sent within 300ms of each other. The
context menu starts to open, but is cleared almost immediately afterwards. After
that, the button no longer shows context menus.

Showing a real context menu on click only happens on ToolbarMenuButton, and
throttling its trigger function will fix the symptom. The core issue is tracked
at crbug.com/661766.

BUG=655556

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

[commit-bot: I haz the power, 2016-11-03 01:18:25]

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