[Webkit-unassigned] [Bug 225559] Implement standards-compliant user gesture tracking

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=225559

--- Comment #2 from Ashley Gullen <ashley at scirra.com> ---
> Do you have a specific use case / test case where Safari's heuristics doesn't work?

- When copying to the clipboard, we have to do some async work to prepare the data to be copied. Currently we use FileReader APIs for that. The async work loses the user gesture and then the copy is blocked. In future we might want to use other APIs to prepare the data to read, such as posting to a worker to process off-thread, DecompressionStream, createImageBitmap, IndexedDB...

- We make a game engine that is capable of running entirely in a Web Worker with OffscreenCanvas. Input events are forwarded to the worker via postMessage() where we then run logic, and any DOM calls are forwarded back to the DOM via postMessage() again. This currently loses the user gesture in Safari and thus blocks our use of OffscreenCanvas in Safari.

> It is actually precisely the fact it allows all APIs to propagate the user activation that is of concern since it would make it hard to identify exactly how this new spec'ed behavior will impact various API's user activation requirement.

Doesn't the simplified model actually make it easier to evaluate?

I'm not clear what is being protected against - surely abusive web content will just make any abusive calls in a synchronous user input event. Blocking a subsequent call up to, say, 1 second later, seems only to block legitimate web content that had to do a bit of async work first.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210511/c280bb3f/attachment-0001.htm>