Chromium is in the business of adding things websites should have no business concerning themselves with, like Bluetooth support, while removing support for useful things: now JPEG XL, previously RSS, MathML.
Yeah, and that's arguably thanks to Igalia and all of their sponsors. They've put a colossal amount of work into this project. If you have the means, it's worth donating for ongoing support, too: https://opencollective.com/mathml-core-support
Google just removed it and would've been content with it staying gone. They said "it wouldn’t have been a good return on investment for us to do it".
I think Bluetooth could similarly be useful for e.g. heart rate monitoring apps for sports.
As the op commented, why not leaving the burden of managing/pairing the heart rate monitoring device to the OS? In the same way audio and input devices work? The only real use case that comes to my mind with Bluetooth support is indeed monitoring, but it’s not about heart rate.
I mean, why not also use it for controlling a LEGO robot from a Scratch app? Configuring presets of your coffee maker without needing a mobile app? Updating the firmware of your soldering iron via vendor web page?
Just providing supervised access to Bluetooth LE would satisfy these all without adding custom interface for all current and all future devices we might want a web page to interact with.
I thought the business was Chrome, whereas Chromium was the open source (and GPLed) project that makes the code that Chrome uses and that would almost certainly not start out as GPLed if it was a new project now.
Having it opt-in also does means most websites can't use it given that the vast majority of their userbase are on default settings.
2: https://bugs.chromium.org/p/chromium/issues/detail?id=117805...