- From: Rick Byers <notifications@github.com>
- Date: Fri, 16 Dec 2016 11:17:06 -0800
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 16 December 2016 19:18:04 UTC
Thanks for raising this Boris. A common use case for Event constructors is to clone / wrap an event with a few changes (eg. I see event delegation libraries do this sometimes). That use case would still be possible, right? In general I think DOM folks (@annevk, @smaug---- IIRC) have said we want event constructors to follow a pretty rigid pattern of just taking the Event attributes directly and not having any smarts / conversions. If we agree to that pattern then I suggest we [proceed with shipping](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/5zb6MESKRog) the constructor as speced now in blink, and explore adding ways to create DataTransfer objects (possibly low priority though). WDYT? -- 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/33#issuecomment-267673557
Received on Friday, 16 December 2016 19:18:04 UTC