mbrodesser

Results 36 comments of mbrodesser

To achieve compatibility across browsers, it should additionally be specified how the selected contents are copied. For instance, when selecting rows in a table, current browser behavior (Chrome, Firefox) when...

At least sanitizing text in `clipboard.readText()` was identified as an issue, see "Issue 5" in step 1.3 of https://w3c.github.io/clipboard-apis/#dom-clipboard-readtext, so that's in scope of this spec.

For the record: Chrome (at least on Ubuntu 20.04) forbids copying when a `contenteditable` element is selected: `data:text/html,AX`. CC @masayuki-nakano

> Ah, yes. We had to deal with this problem specifically with Pages. The justification of their behavior comes from: > https://developer.apple.com/documentation/appkit/nspasteboard/1533561-declaretypes?language=objc > > > The types should be ordered...

Related to this: why do `read()`/`write()` take/return multiple `ClipboardItem`s, when each `ClipboardItem` may contain may contain multiple types? Shouldn't either exactly one `ClipboardItem` with multiple types or multiple `ClipboardItem`s with...

More research about the issue lead to https://blog.tomayac.com/2020/03/20/multi-mime-type-copying-with-the-async-clipboard-api/#copying-an-image, which links to https://support.microsoft.com/en-us/topic/copy-and-paste-using-the-office-clipboard-714a72af-1ad4-450f-8708-c2931e73ec8a?ui=en-us&rs=en-us&ad=us#ID0EAABAAA=Windows. Apparently, Microsoft Office indeed supports multiple clipboard items (up to 24). So I guess a future use-case could...

> I think the issue in OP remains, no? That article also mentions that implementations might not do this? Yes. Blink's idl interface takes multiple `ClipboardItem`s, but [throws an exception...

> Copying multiple items where each item has multiple representation is a thing in iOS & iPadOS. e.g. you can select multiple images in Photos and copy them over to...

@lgarron: are you still working on this PR? The change itself is desirable, it just requires slight adaptation to match the current base.

@lgarron: just to be sure, do you still intend adapting this patch soon? It would be valuable.