User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.101 Safari/537.36 Steps to reproduce: nfc_worker.js does not maintain Callback map. Without this previous callback maybe overriden in some race conditions leading to some undesired behaviours

What's this bug used for? What's the impact?

This is 'nice to have' fix in nfc_worker. Also there is an ongoing effort to port nfc_worker.js to its C++ version (not sure of its current status). If the port were to happen at the earliest, then we need not have to fix anything in the java script implementation of the worker (since it would have moved to c++ version anyways). That said, if we stick to current java script implementation, I would assume that we may have couple of issues in extreme conditions where the DUT (device under test) is subjected to heavy Nfc testing. In a normal testing mode and user scenarios this may not be an issue.

As the worker will be re-written in C++, close this as WONTFIX.