Comment 4 for bug 1572154

I find that on tapping Cancel after entering a search query, the scope's run() method executes twice. This seems to be not hanlded well by scope-aggregator.

For example: calls-scope always prints "CALLS starting" on entering run():
While watching scope-registry.log:
(launch or refresh calls-scope)
CAllS starting
(enter query string)
CALLS starting
(tap Cancel)
CALLS starting
CALLS starting

There should not be two entries after tapping cancel.