[cross-posted] There has been a lot of debate [1][2] about the correct name for device independent events [3] as a concept*. We have considered Intention Events, Command Events, and Action Events among others. I believe we now have a good name for them- Responsive Input Events. The reason for this name is that it is the corollary to Responsive Layout: for input instead of output. Together these two concepts can help form the basis of Responsive Design going forward.
This could potentially apply to areas outside of editing in the future, so if anyone has further feedback on this name we should get it locked down now so we have a consistent story going forward. Let me know if you have feedback! Ben * the concept is summarized in the Explainer [3] Introduction as "Today, sites mostly respond to Device-Specific Input directly, causing several issues including difficultly understanding what a user intends, complexity in building Accessible sites, and complex localization. This document is meant to describe the path forward for Responsive Input across multiple areas so that sites can be written more simply across devices and input modalities in an Accessible and future-ready way." [1] https://github.com/w3c/editing-explainer/issues/7 [2] https://www.w3.org/Search/Mail/Public/search?keywords=&hdr-1-name=subject&hdr-1-query=Need+Agreement+on+Terminology&index-grp=Public_FULL&index-type=t&type-index=public-editing-tf [3] http://w3c.github.io/editing-explainer/responsive-input-explainer.html
