Re: [editing] Should Device-Specific Input Events say what Responsive Input Event they will cause? (#25)

Device-specific input events *should* say what behaviour they trigger. But for authors using them, they presumably want to define the behaviour in case the DI event isn't really handled.

onSomeDeviceAction(evt) {
  if (responsiveEvent)
  fireResponsiveEvent(theOneIwant);
 else 
  doTheResponsiveEventThingManually(evt);
}

The benefit to the author being that the platform implementation is likely more efficient?

The drawback being a mess of testing and figuring out if implementations *really* do what they claim. But how else do we get "casual" authors there from here?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/25#issuecomment-108279574

Received on Wednesday, 3 June 2015 09:52:30 UTC