- From: Joshua Bell <notifications@github.com>
- Date: Fri, 19 Jan 2018 01:37:13 +0000 (UTC)
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 19 January 2018 01:37:39 UTC
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: new DataTransfer}` as the options. Firefox provides a default DataTransfer instance. Two problems: * [ ] The spec doesn't describe how the constructor works. * [ ] The spec prose has _"The clipboardData attribute is an instance of the DataTransfer interface"_ but the IDL has `readonly attribute DataTransfer? clipboardData;` - these seem to disagree on nullability. I'd expect the constructor prose to say something like "If _eventInitDict_ is not given, or _eventInitDict_'s _clipboardData_ dictionary member is null, then initialize _event_'s **clipboardData** to a newly created `DataTransfer` object." to fix the first point. But then the second point is weird - how do you get a null in there? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/issues/64
Received on Friday, 19 January 2018 01:37:39 UTC