Re: [web-bluetooth] Use AbortController instead of stop method (#439)

I haven't thought about `AbortController` vs `stop()` enough to have strong opinions, but @gfwilliams, the worry that the program will "accidentally call `watchAdvertisements` with no signal" is no different from worrying that the program will fail to call `.stop()`. In both cases, at the point the programmer realizes that the program needs to stop scanning, they can modify the program to do what it needs to do to stop scanning. We don't modify programs while they're running or persist this part of their state to storage, so the ability to forget to pass the signal in one run doesn't make it any harder to pass the signal in the next run.

-- 
GitHub Notification of comment by jyasskin
Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/439#issuecomment-663138601 using your GitHub account

Received on Thursday, 23 July 2020 17:36:59 UTC