It doesn't make sense that each event in the browser has one "target". When you move two touches at the same time on two different dom nodes, that event should be modeled as a single Event with two separate changed touches, and each touch has their own target. Instead, today the browser fires two separate events back to back, each with their own separate target and only one changed touch each