clipboard-apis
clipboard-apis copied to clipboard
w3c
Clipboard API and events
[ClipboardItem.lastModified](https://w3c.github.io/clipboard-apis/#dom-clipboarditem-lastmodified) is currently defined as `long long`. It probably should be `unsigned long long`, but [DOMTimeStamp](https://developer.mozilla.org/en-US/docs/Web/API/DOMTimeStamp) seems like an even better choice. Is there a good reason to keep this...
I stumble up on something abnormal behavior when i tried to copy a jpeg with exif rotation and reading it from the clipboard api. First of all, when i read...
As browsers roll out implementation, websites will find themselves in a situation where they may want the user to paste certain data types (e.g. a specific image format). At the...
Right now, the spec is not clear about how unsupported data types should be handled in `write()`. I think there are a few reasonable options: - Return which data types...
We should consider defining a way for JS to determine the set of data types that the UA supports for reading/writing. Currently, we have a list of supported types in...
Currently the source uses: `` Bikeshed does a better job if you use: `` * better formatting - algorithms are wrapped in a block * variable checks - bikeshed can...
Per https://bugs.chromium.org/p/chromium/issues/detail?id=800742 In Chrome 63, this results in null: `new ClipboardEvent('paste').clipboardData` - there's no code to populate the event's clipboardData with anything if it's not provided e.g. by passing `{clipboardData:...
In the [WebApps charter](https://www.w3.org/2019/05/webapps-charter.html#scope) it says: >Where there are implications for implementors, developers, or users, in the areas of accessibility, internationalization, privacy, and security, each specification must have a section...
There may or may not be any internationalization concerns with the spec, but we should make sure to have an "Internationalization Considerations" section stating that we've taken i18n into consideration....
The [Async Clipboard API](https://www.w3.org/TR/clipboard-apis/#async-clipboard-api) doesn't already restrict API use to top-level origins, but other potentially dangerous APIs like [screen share](https://w3c.github.io/mediacapture-screen-share/#feature-policy-integration-0) do. Using a feature policy to restrict usage to top-level...
