Adding manufacturer id filtering support would help some web developers today.
For info, the simple manufacturerId filter was removed in favor of a more sophisticated one long time ago but I believe it may worth exploring having both.
I have a simple CL that works just fine at https://chromium-review.googlesource.com/c/chromium/src/+/2825891. What do you folks think? @reillyeon @scheib
const device = await navigator.bluetooth.requestDevice({ filters: [{ manufacturerId: 0x00e0 }] });Side note: While I was playing with it on macOS, I've noticed there was only one unique manufacturer data key (the last one set in advertisement flags) while other platforms support multiple ones as described in the Bluetooth spec. We may want to rethink manufacturerData then as it allows several ones today in the spec.
Adding manufacturer id filtering support would help some web developers today.
For info, the simple
manufacturerIdfilter was removed in favor of a more sophisticated one long time ago but I believe it may worth exploring having both.I have a simple CL that works just fine at https://chromium-review.googlesource.com/c/chromium/src/+/2825891. What do you folks think? @reillyeon @scheib
Side note: While I was playing with it on macOS, I've noticed there was only one unique manufacturer data key (the last one set in advertisement flags) while other platforms support multiple ones as described in the Bluetooth spec. We may want to rethink
manufacturerDatathen as it allows several ones today in the spec.