If you're using event pages, store the identifier in (don't forget to set the storage permission in the manifest file). This can be achieved by generating an unique (to the session) identifier. Instead of cleaning up on shutdown, just make sure that old alarms are not run on startup. It's not possible for a Chrome extension to reliably run some code when the browser closes. If your storage will change frequently then there are better approaches than this one.but the key thing to remember for whatever implementation your choose is to not to mix up synchronous and asynchronous events. Then from the webRequest listener you could say return Remember that the Back gesture actually works in two places. The easiest would be to store the values of the local storage inside some variable when your extension is loaded (call it, say, storage_cache). Another option worth remembering: You can also swipe in with two fingers together to open an. There are a couple of ways that you can make this work. The rest of your code continues to run and nothing is returned from your webRequest listener.the return statement) is not executed immediately and will be run at some later time If it is, then make an asynchronous call to.Before the webrequest, check if the url is.The basic run-through of what is happening with the code you have is: The chrome.storage api is asynchronous, so the approach that you are taking here will not work.
0 kommentar(er)
