Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

As discussed previously, instead of the original planned deprecation, we've added human-readable names for the Bluetooth assigned numbers to the Bluetooth spec. See https://github.com/WebBluetoothCG/web-bluetooth/pull/560 and https://github.com/WebBluetoothCG/registries/pull/29 Thank you Blink API

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

Yes. It has no impact on any permission surfaces. On Tue, Aug 31, 2021 at 5:14 PM Balazs Engedy wrote: > Just to double-check: this is purely a web-facing change, and has no > impact on any permission surfaces. Is that correct? > > On Friday, August 20, 2021 at 9:26:57 PM UTC+2 Reilly Grant wrot

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

Just to double-check: this is purely a web-facing change, and has no impact on any permission surfaces. Is that correct? On Friday, August 20, 2021 at 9:26:57 PM UTC+2 Reilly Grant wrote: > Thanks for the feedback! > > Reilly Grant | Software Engineer | reil...@chromium.org | Google Chrome >

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

Thanks for the feedback! Reilly Grant | Software Engineer | reil...@chromium.org | Google Chrome On Fri, Aug 20, 2021 at 7:07 AM François Beaufort 🇫🇷 wrote: > Thank you everyone! > We'll work on updating the spec >

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

Thank you everyone! We'll work on updating the spec and come back to you when it's done. On Fri, Aug 20, 2021 at 11:14 AM Thomas Steiner wrote: > > That leads me to believe that the best path forward is to specify the > mapping table dir

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

> That leads me to believe that the best path forward is to specify the mapping table directly in the Web Bluetooth specification. At that point we then have the option of continuing to update it as the Bluetooth SIG declares additional assigned numbers or leave it static. Love it. This seems like

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

On Thu, Aug 19, 2021 at 11:41 PM Chris Harrelson wrote: > On Thu, Aug 19, 2021 at 8:10 AM Reilly Grant wrote: > >> That leads me to believe that the best path forward is to specify the >> mapping table directly in the Web Bluetooth specification. At that point we >> then have the option of cont

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

On Thu, Aug 19, 2021 at 8:10 AM Reilly Grant wrote: > That leads me to believe that the best path forward is to specify the > mapping table directly in the Web Bluetooth specification. At that point we > then have the option of continuing to update it as the Bluetooth SIG > declares additional a

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

The motivation behind the deprecation is the discovery (from the linked issue ) that the Bluetooth SIG is no longer maintaining the mapping table which we originally used for defining these aliases. At this point the Chromium implementatio

Re: [blink-dev] Intent to Deprecate: Human-readable names for Bluetooth assigned numbers

We typically avoid deprecation warnings with no end date. It's also not clear to me what the benefit of developers following the warning is. Isn't it enough that we won't add future human readable names? On Tue, Aug 17, 2021 at 2:24 PM François Beaufort 🇫🇷 wrote: > Yes. The console deprecation w