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

johanneswilm left a comment (w3c/clipboard-apis#240)

TPAC 2025:
> Rohan
I hope everyone is aware of this proposal to optimize MIME type reading 
We want to optimize where the web author can request specific MIME types
We have two options, one was to specifically ask for a set of MIME types
The second option can cause certain backward compatibility challenges
This changes the behaviour of the clipboard item as well
With this change, this will give you the latest data every time it is called
We were concerned that some website were replying on the clipboard 
To have a persistent state 
Say a clipboard timeline application
So there was a backward compatibility list
To move forward we have added this in chromium
There are a few more concern around this
The backward compatibility issue
The user permission part
So if we are moving the read to the get type, do we want to move the
Permission to getType. 
The other scenario is that you do the permission first. 
Since the permission is refused.
Smaug
The permission model is where this is difficult
They were not expecting and error from getType
Rohan
If the clipboard changes between then it throws an error
But there are some backward compatibility issues that we want to see if there are actually issues here
Johannes
What are the backwards compatibility issues here
Smaug
If you give the permission once, then it has that access forever?
Rohan
Yes, but you can manually deny that permission in settings
So if the use denies the permission then it 
Smaug
This seems a very unlikely scenario 
Rohan
What if the clipboard never changes and the clipboard item and they might just what to read it later
Johannes
You are collecting telemetry data on this?
What exactly are you collecting
Rohan
We are, and checking to see if this permission changes
Johannes
This is only an issue if we have old clipboard items around 
Rohan
This only matters if they have a cache
Johannes
They could read it later and that’s when there’s an issue later
If this is an issue, it’s only for Chromium
If the telemetry data shows that this isn’t really being done, so that would show that it’s not really an issue
Get back to us when we have the telemetry data?


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

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