In http://trac.webkit.org/changeset/65964 a UserGestureIndicator was introduced in chromium's webkit layer for all input events (later restricted to a subset of input events such as clicks). But even with the restriction, this still creates two consumable gestures (there's also one in WebCore/page/EventHandler for mouse events. I guess initially this was supposed to protect against opening multiple windows from a single user gesture (chrome consumes a user gesture for each new window), however, now a web page can open two windows per event
Created attachment 163348 [details] Patch
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
It seems like the old code can just be removed. I'm currently building on mac to see what wtr does with the test.
Fails on both wk1 and wk2 :-/ Is it preferable to skip the layout test or move to to platform/chromium?
Comment on attachment 163348 [details] Patch I'd put it in platform/chromium because consumable user gestures are only used by chromium.
Created attachment 163411 [details] Patch
Comment on attachment 163411 [details] Patch meh fast/events/popup-blocking-timers.html seems to rely on creating a ton of popups with a single user event I guess I need to rewrite the test to generate an equal amount of clicks.
Comment on attachment 163411 [details] Patch Attachment 163411 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/13824370 New failing tests: fast/events/popup-blocking-timers.html
Comment on attachment 163411 [details] Patch Clearing flags on attachment: 163411 Committed r128273: <http://trac.webkit.org/changeset/128273>
All reviewed patches have been landed. Closing bug.