- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 May 2024 05:15:26 +0000
- To: public-geolocation@w3.org
> The realities of physics haven't changed, so I wouldn't expect different results, except that you are retrofitting to an API that is not designed to be extensible. How is it not extensible? I don't see any issue with bringing the things you listed above to the Device Orientation and Motion spec? Given the lack of interest from other implementers in the additional specifications, it may be more effective to integrate that functionality into the existing ones. The current approach seems to conflict with the TAG's [new features](https://www.w3.org/TR/design-principles/#new-features) design principles. According to these principles: "Before adding items, consider integration with existing, similar capabilities." It appears that there was limited effort to integrate similar capabilities, leading to specifications that are implemented by only one engine and are not adopted by other browser vendors. Wouldn't it be better to add the functionality to this spec (which we should do regardless)? -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/182#issuecomment-2121757409 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 May 2024 05:15:27 UTC