Re: [w3c/clipboard-apis] Selective Clipboard Format Read (Issue #240)

css-meeting-bot left a comment (w3c/clipboard-apis#240)

The Web Editing Working Group just discussed `Selective clipboard format read`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dandclark> topic: Selective clipboard format read<br>
&lt;dandclark> github: https://github.com/w3c/clipboard-apis/issues/240<br>
&lt;dandclark> Ashish: Last time we discussed adding telemetry<br>
&lt;whsieh> discussion: add telemetry<br>
&lt;whsieh> (oh, thanks for scribing dan!)<br>
&lt;dandclark> ...to see if we should move ahead with making getType() lazy<br>
&lt;dandclark> ...based on telemetry so far the instances where data chantged between calls is 1 in a million pageloads<br>
&lt;dandclark> ...so if we make getType lazy it could throw, or return empty string, if data is stale<br>
&lt;dandclark> ...throwing has higher compat risk for Chromium<br>
&lt;dandclark> ...would Safari be willing to make change to return empty change for stale data if Chromium changes getType to be lazy?<br>
&lt;dandclark> whsieh: instead of throwing ex, return empty string? Seems OK<br>
&lt;dandclark> ...willing to do that if we don't already<br>
&lt;dandclark> Ashish: And would FF be willing to change to this behavior?<br>
&lt;dandclark> ...if Chromium goes first<br>
&lt;dandclark> whsieh: Do we have anyone from FF on the call?<br>
&lt;dandclark> ...don't think so<br>
&lt;dandclark> dandclark: Ashish can you follow up with Olli in the thread?<br>
&lt;dandclark> Ashish: Yes<br>
&lt;dandclark> ...One more point regarding what to do if getType is called when document not in focus<br>
&lt;dandclark> ...currently we don't allow the read when not focused<br>
&lt;dandclark> ...But getType call succeeds when window is not in focused. Should we change this if getType is made lazy?<br>
&lt;dandclark> whsieh: As long as items have been read when document has focus<br>
&lt;dandclark> Ashish:  But we're not reading data unless we have getType<br>
&lt;dandclark> whsieh: Focus restriction is only for getting items<br>
&lt;dandclark> ...even in background, can get data that was lazily delivered<br>
&lt;dandclark> whsieh: Might be compat issue if we started restricting getting type when document is in background<br>
&lt;dandclark> ...from WebKit perspective, probably safer to keep status quo, allow reading in background as long as items were obtained when you were active<br>
&lt;dandclark> dandclark: We should have WPTs<br>
&lt;dandclark> whsieh: Can you focus away from window in WPT<br>
&lt;dandclark> dandclark: I think you can have popup<br>
&lt;whsieh> https://github.com/w3c/input-events/issues/176<br>
&lt;dandclark> Rohan?: Or use iframe<br>
&lt;dandclark> johanneswilm: This has been mentioned before, we took up at TPAC<br>
&lt;dandclark> ...is the question of being able to isolate the composition<br>
&lt;dandclark> ...comments from Masayuki, some new data<br>
&lt;dandclark> ...Anyone from Mozilla want to discuss?<br>
&lt;dandclark> ...Masayuki implemented something not to spec to get around this problem<br>
&lt;dandclark> ...related to spec change he proposed in 2018<br>
&lt;dandclark> ...Let's wait until we have Mozilla people<br>
&lt;whsieh> https://github.com/w3c/input-events/issues/177<br>
&lt;dandclark> johanneswilm: Issue with WPTs that were introduced<br>
&lt;dandclark> ...Looks related to Chromium<br>
&lt;dandclark> ...Can we get someone to take a look?<br>
&lt;dandclark> dandclark: Rakesh could you follow up with Utkarsh re: https://chromium-review.googlesource.com/c/chromium/src/+/5443103 ?<br>
&lt;dandclark> ...to answer questions on the github issue?<br>
</details>


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

Message ID: <w3c/clipboard-apis/issues/240/3724639219@github.com>