I find the requestLEScan a bit weird, first of all, it returns BluetoothLEScan when it resolves which has the same info that you just set as part of calling requestLEScan so maybe not that useful. Also, it has a `stop` method, but today newer APIs will be using the AbortController instead @francoisbeaufort -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/333#issuecomment-529792666
Received on Tuesday, 10 September 2019 06:35:10 UTC