Re: [touch-events] TouchEvent constructor is very unusual since it converts one type of object (sequence) to another type (TouchList)

I think I could live with adding just prose defining how TouchLists 
are created.
Tough the API would look more consistent if TouchList had the ctor and
 then one would pass those to event ctor. But if you think removing 
support for sequence<Touch> in EventDict is too late, I guess we just 
have to go with the next simplest approach, which is to support only 
sequence<Touch> and describe in prose how to create the lists. 

GitHub Notification of comment by smaug----
Please view or discuss this issue at 
using your GitHub account

Received on Tuesday, 22 December 2015 22:01:57 UTC