Re: [w3ctag/design-reviews] Web Bluetooth Scanning (#333)

> We took this up during a breakout during the Tokyo F2F. I second the remarks @kenchris made above. Comments and questions follow:
> 
> 1. This should probably be a feature that only works on the currently focused window.

Yes, that is what we're doing in Chrome.  When the window loses focus, we stop the scan.

> 2. Otherwise, normative reject conditions under race would be extremely helpful for other implementors (e.g. two tabs scanning at the same time - is this possible?)

Yes, you can have two tabs scanning at the same time.  

> 3. We'd be more happy if this feature was a active tab (Point 1 in this list) only feature, as it can be power consuming for mobile devices and has privacy consideration. A visual indicator (like we do with audio) when scanning could be useful.

Agreed about active tab/window only.  The visual indicator is a nice idea, but it's not something that I think we should spec out.

> 4. Following those thoughts, a grace period for blurred tabs (e.g. if user moved focus to a different tab for more than n seconds right after starting a scan, stop scanning) sounds like a potential mitigation for racing (or wasting resources) while adding some safety.

I do not follow this thought.





-- 
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-533841582