snianu
snianu
### WebKittens @annevk @whsieh ### Title of the spec Feature detection for supported clipboard formats ### URL to the spec https://w3c.github.io/clipboard-apis/#clipboard-item-interface, https://w3c.github.io/clipboard-apis/#dom-clipboarditem-supports ### URL to the spec's repository https://w3c.github.io/clipboard-apis/#clipboard-item-interface, https://w3c.github.io/clipboard-apis/#dom-clipboarditem-supports...
Reading *all* supported formats from the clipboard during read() takes time especially since the HTML/Image payload can be in MBs/GBs. We could defer reading of the actual data from the...
Copied from https://github.com/w3c/editing/issues/423#issuecomment-1858535412. @saschanaz said: > Hmm, I was not fully understanding this issue back in the meeting, as my focus was on a different issue. To reiterate what @smaug----...
On Windows, according to the [mdn doc](https://learn.microsoft.com/en-us/windows/win32/dataxchg/html-clipboard-format), native apps need to write `` and `` tags to indicate the fragment start and end in the HTML markup. This information is...
`ClipboardItem` has `ClipboardItemDataType` which is a `Promise` to `Blob or DOMString`. When web authors don't resolve these promises in a reasonable amount of time, what should the Browser do in...
In Chromium browsers, the data from the system clipboard is accessed asynchronously from Browser process (that calls the system clipboard APIs). When the browser reads the clipboard data, it will...
Popular native apps on Windows read formats like `image/svg+xml` in UTF-8 form [1]. In the spec, before the payload for a format gets written to the clipboard, the content is...