- From: Lars Knudsen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Apr 2023 18:42:20 +0000
- To: public-web-bluetooth-log@w3.org
> I'm struggling to find examples of how platform APIs handle receiving Extended Advertising data. If there isn't anything an application needs to do different to receive such data then it should already work in existing Web Bluetooth implementations, though it would be good to update the specification to explicitly mention it. It's a different type of response than legacy advertising and scan response, so it has to be included/handled explicitly. Also, I did a quick check against a device advertising both legacy and extended (with the same bt name) and only the legacy data came up (using the watch Advertisements demo page) -- GitHub Notification of comment by larsgk Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/604#issuecomment-1513635843 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 April 2023 18:42:22 UTC