Bug 162806 – [iOS] Allow sequence<Touch> input in TouchEvent constructor

• Component: DOM
• Status: RESOLVED FIXED

[Chris Dumez]

Allow sequence<Touch> input in TouchEvent constructor in addition to TouchList object. It is convenient for developers to pass arrays of Touch objects.

[Chris Dumez]

<rdar://problem/28566429>

[Chris Dumez]

Created attachment 290388 [details]
Patch

[Ryosuke Niwa]

Can't we do this by just overloading constructors instead?

[Chris Dumez]

(In reply to comment #3)
> Can't we do this by just overloading constructors instead?

Not really, the constructor looks like so:

dictionary TouchEventInit : EventModifierInit {
    TouchList touches;
    TouchList targetTouches;
    TouchList changedTouches;
};

[Constructor(DOMString type, optional TouchEventInit eventInitDict)]

I think the clean way (once we support union) and once we use proper constructors for event interfaces (instead of [ConstructorTemplate=Event] / [InitializedByEventConstructor]) would be:

dictionary TouchEventInit : EventModifierInit {
    (TouchList or sequence<Touch>) touches = [];
    (TouchList or sequence<Touch>) targetTouches = [];
    (TouchList or sequence<Touch>) changedTouches = [];
};

But we do not support unions just yet.

[Chris Dumez]

Comment on attachment 290388 [details]
Patch

Clearing flags on attachment: 290388

Committed r206681: <http://trac.webkit.org/changeset/206681>

[Chris Dumez]

All reviewed patches have been landed.  Closing bug.