Re: [vibration] Update implementation report (#33)

@reillyeon, would you mind updating the title of this issue to "Proposal to obsolete this Recommendation"? 🙏 

@anssiko, which second independent implementation would meet the requirement? 

> e.g. https://caniuse.com/vibration that keeps track of other browsers. 

Note that you need _**other engines**_, not other "browsers". If those are all Chromium variants, then that doesn't count as independent implementations and this is still in violation and should be Obsoleted.

**Chromium Engine**
- **Chrome**: Chromium
- **Edge**: Chromium
- **Opera**: Chromium
- **Chrome for Android**: Chromium
- **Samsung Internet**: Chromium
- **Opera Mobile**: Chromium
- **UC Browser for Android**: Chromium
- **QQ Browser**: Chromium 
- **Baidu Browser**: Chromium

So, where is the second implementation with actual/significant users? (i.e., something worthy of a W3C Recommendation)?  

> With time, it might be that the baseline LCD will move so that we can update this API to consider new features. One of the possible such features under consideration is strength control https://github.com/w3c/vibration/issues/17 that might be soon about to reach the level it could be considered. Contributions welcome in this area too from interested folks.

It would be terrible bad if DAS again started working on anything related to this without participation from other implementers. It's also not in Scope of DAS's charter to do haptics:
https://www.w3.org/2024/02/das-wg-charter.html#scope

what would this fall under? The charter says that Vibration is only in maintenance mode new features wouldn't be in scope of DAS's charter.  




-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/vibration/issues/33#issuecomment-2121648150 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 03:23:32 UTC