Re: [w3c/clipboard-apis] Don't recommend user gesture in clipboard API (#75)

The Web Editing Working Group just discussed `Don't recommend user gesture in clipboard API`.

<details><summary>The full IRC log of that discussion</summary>
&lt;Travis> topic: Don't recommend user gesture in clipboard API<br>
&lt;Travis> github: https://github.com/w3c/clipboard-apis/issues/75<br>
&lt;Travis> johanneswilm: last time the action was whsieh will check user-activation spec and propose number of seconds.<br>
&lt;Travis> .. and BoCupp said 1s seems reasonable.<br>
&lt;Travis> whsieh: I haven't yet decided on a specific value of seconds... :(<br>
&lt;Travis> .. I think we should just start with 1s and increase if needed.<br>
&lt;Travis> BoCupp: refresher: why the number of seconds? (Can't remember the details)<br>
&lt;Travis> .. when writing to clipboard you can write immediately. Waiting on the network, etc., isn't a problem except for the timing of performing the write call.<br>
&lt;Travis> whsieh: in this case the requestor doesn't know whether they want to call clipboard write during the user gesture.<br>
&lt;Travis> johanneswilm: e.g., in remote desktop they don't know if anything's on the clipboard.<br>
&lt;Travis> .. do I hear correctly that 1s is the recommendation?<br>
&lt;Travis> whsieh: I think we should start more conservatively. Chrome/Firefox time is currently 5s.<br>
&lt;Travis> .. Webkit's user activation time is 1s everywhere else. This would match everything else.<br>
&lt;Travis> .. then eventually we could move everything to match other browser (user-activation time delay to perhaps 5s)<br>
&lt;Travis> .. right now there is no delay--it has to be during the event handler.<br>
&lt;Travis> BoCupp: Even in navigator.clipboard.write?<br>
&lt;Travis> whsieh: yes, in webkit.<br>
&lt;Travis> .. like touchstart--other things we consider user activation.<br>
&lt;Travis> .. it has to be synchronously as part of the user gesture (no async stuff)<br>
&lt;Travis> johanneswilm: So, 1s? Will other browsers change?<br>
&lt;Travis> BoCupp: I feel like (no number of seconds) will ever be enough for some of these scenarios.<br>
&lt;Travis> johanneswilm: should there be a minimum?<br>
&lt;Travis> .. e.g., in firefox it's 5s? But other browsers have faster times (500ms), then it will break everywhere else.<br>
&lt;Travis> .. but if it's written down as 1s, then there's an expectation set.<br>
&lt;Travis> BoCupp: I'm not inclinded to write the 1s (or other time) anywhere. Would rather provide affordances for delaying rather than just changing the number of seconds for this [edge case].<br>
&lt;Travis> .. 5s seems like a really long time for a user-gesture...<br>
&lt;Travis> BoCupp: Would like to say in the issue--not likely to change this. There's no guarantee that this will solve all use cases...<br>
&lt;Travis> .. wondering if this is the kind of issue we don't need to put in the spec.<br>
&lt;Travis> whsieh: having some delay (in WebKit) would help, since there's currently no delay.<br>
&lt;Travis> johanneswilm: So, we don't want to specify any value, but should just say some amount of time?<br>
&lt;Travis> BoCupp: If we did say it, we wouldn't put it in our spec... should probably go to user-activation spec?<br>
&lt;Travis> .. increasing the seconds to solve this problem isn't really solving the problem.<br>
&lt;Travis> .. I do like having a consideration for introducing an async delay.<br>
&lt;Travis> .. I like the idea of having whsieh post to the issue and indicate they may take some action...<br>
&lt;Travis> action: whsieh to post to the issue and indicate a plan to make an adjustment to support async delay of some sort to handle this scenario.<br>
</details>


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/75#issuecomment-1125148793
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/clipboard-apis/issues/75/1125148793@github.com>