- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Apr 2017 05:21:13 +0000
- To: public-web-bluetooth-log@w3.org
The main risk here is that it's almost certainly better to just live with the mis-spelling then to try to fix it but fail (due to web compat) to remove the old name and so get stuck having both indefinitely. Nobody else has implemented this as far as you know, right? And usage is probably quite low? Do you already have a UseCounter for WebBluetooth which would provide an upper-bound on the risk here? Assuming we have evidence that the usage is pretty low then I'd suggest just making a concrete plan to deprecate/remove the old name by a specific milestone and ship the new event at the same time as deprecating the old one. Hopefully you can get away with just firing both events during the transition period (rather than trying to do something complicated like we do for `mousewheel` where it's fired only when a listener for `wheel` wasn't invoked to prevent double handling). Of course it's up to you guys whether the benefit of fixing the name is worth this hassle. But as long as the usage is low hopefully the hassle/pain is really small... -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/363#issuecomment-294407200 using your GitHub account
Received on Monday, 17 April 2017 05:21:20 UTC