Tabs seem to cease executing our content script, or at least stop listening to onConnect/onPortMessage events, after a file is downloaded in a given tab (even if Chrome just displayed a file browser dialog and the user cancelled it).
If investigation determines that this is the fault of Chrome and we have no way around it, submit a bug to crbug.com.
Tabs seem to cease executing our content script, or at least stop listening to onConnect/onPortMessage events, after a file is downloaded in a given tab (even if Chrome just displayed a file browser dialog and the user cancelled it).
If investigation determines that this is the fault of Chrome and we have no way around it, submit a bug to crbug.com.