Intent to Implement: Pointer Events in Chrome

Re:Intent to Implement: Pointer Events in Chrome by existencebox on Wednesday March 25, 2015 @04:26PM (#9265690)

Disclaimer: I am primarily a systems guy, and extremely green in all things web.

Why wouldn't a concept of "event inheritence" be valuable here? Pointer events could be both touch or click events; and the consumer can chose due to the type specified which they want to fire on.

I understand this isn't the model that events have been built under in web proper, but if I'm grokking the conflict here (there's a large chance I'm missing some key point, even reading the spec took some hand waving to put it together in my head) it's largely constrained by the inflexibility of what an event is.

(I'd be very curious for any sort of "why I'm wrong" or "why this isn't feasible/desirable")

[ Parent | on HN ]

Re:Intent to Implement: Pointer Events in Chrome by mbrubeck on Wednesday March 25, 2015 @04:56PM (#9265860)

DOM events do form an inheritance hierarchy. For example, TouchEvent and MouseEvent both inherit from UIEvent.

But for compatibility reasons, we can't make arbitrary changes to legacy APIs. So rather than, say, change MouseEvent to be a subtype of PointerEvent, we have to do the reverse and have PointerEvent extend MouseEvent.

[ Parent | on HN ]

Re:Intent to Implement: Pointer Events in Chrome by nevir on Thursday March 26, 2015 @02:35AM (#9268114)

Or introduce a whole new hierarchy.

[ Parent | on HN ]