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

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. 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/touch-events/issues/54#issuecomment-166742082