@reillyeon, I don't think we should include "Event"... in the title. The spec provides a Model for device orientation and motion, which then are expressed in the API as events. But like with other specs, (e.g., Fetch, Permissions, Screen orientation, etc.) we generally wouldn't put how it's represented as the API in the title.
To be sure, if one Googles, Bings, or even searches on DuckDuckGo, for "device orientation and motion spec" the spec is already found - so this wouldn't affect how findable this spec is.
@reillyeon, I don't think we should include "Event"... in the title. The spec provides a Model for device orientation and motion, which then are expressed in the API as events. But like with other specs, (e.g., Fetch, Permissions, Screen orientation, etc.) we generally wouldn't put how it's represented as the API in the title.
To be sure, if one Googles, Bings, or even searches on DuckDuckGo, for "device orientation and motion spec" the spec is already found - so this wouldn't affect how findable this spec is.
Preview | Diff