[web-nfc] Get rid of filtering + AbortController (#560)

kenchris has just created a new issue for https://github.com/w3c/web-nfc:

== Get rid of filtering + AbortController ==
It turns out that filtering was not the greatest idea

* it is a bit confusing as it is not filtering the records (not sure that would actually be that useful without complex rules) and it just filters whether such a record exist 
* Newer standards like TNEP have other ways of selecting services as a way of filtering/communicating with IoT devices.

So let's get rid of it and simplify spec and implementation. @zolkis 

Also, lots of thought around AbortController with TAG members.

`scan` is a continuously running operation until cancelled, (or loss of focus etc) and not just a long running task, so me and others have come to the conclusion that AbortController is not the proper way to cancel our scans. I suggest that we follow Generic Sensors instead and introduce a `start()` and `stop()` method instead.

Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/560 using your GitHub account

Received on Wednesday, 22 April 2020 13:52:22 UTC