- From: Rick Waldron <waldron.rick@gmail.com>
- Date: Thu, 22 Aug 2013 13:28:39 -0400
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Brian Chirls <brian.chirls@gmail.com>, Simon Pieters <simonp@opera.com>
On Wednesday, August 21, 2013, Tab Atkins Jr. wrote: > On Wed, Aug 21, 2013 at 7:43 AM, Rick Waldron <waldron.rick@gmail.com> > wrote: > > Ideally the event.target is defined more specifically, eg. if event > objects > > from clicks (and others) on controls had an event.target that was the > > actual controls element. > > What "actual controls element"? There is no such thing. I guess I incorrectly assumed that the video element controls in the shadow subtree could stand in here—sorry for creating confusion and thanks for setting it straight. Rick > > Again, events based on the actual actions are the way to go. If > you're trying to track user's behavior in some way, what happens if > you're listening for clicks on the controls but they instead do a > right-click on the video and select "pause" from there? The scenario > you're trying to defend is broken from the start. :/ > > ~TJ >
Received on Thursday, 22 August 2013 17:29:08 UTC