Changes between Version 1 and Version 2 of Ticket #1843, comment 4


Ignore:
Timestamp:
01/22/2015 04:05:52 PM (5 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1843, comment 4

    v1 v2  
    1 As I said you might still need to communicate between frames to undo all DOM modifications. And waiting for an error (usually triggered by user interaction) isn't as smooth as immediately reverting DOM modifications when the extension is unloaded. This is what the user expects when he disables/uninstalls an extension after all. 
     1As I said you might still need to communicate between frames to undo all DOM modifications. And waiting for an error (usually triggered by user interaction) isn't as smooth as immediately reverting DOM modifications when the extension is unloaded. This is what the user expects when he disables/uninstalls an extension after all. Also you might not be able to catch those errors, if they occur asynchronously. 
    22 
    33However, it might be possible to create a port with `chrome.runtime.connect()` and listen to it's `onDisconnected` event. It should be fired in the content script when the background page dies. Then we could implement `ext.onExtensionUnloaded` using ports under the hood. Can you check that?