--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/99ae6c6f-79d6-4df7-b45c-2e2847572d01n%40chromium.org.
Hi,I don't need to forbid the user to do anything.I need tabs.onRemoved to work the same way when closing the browser as when closing the tab. Or you need another API method to do the work when you close the browser.Thanks.--вторник, 5 сентября 2023 г. в 05:17:57 UTC+3, Cuyler Stuwe:You can’t prevent the user from closing the browser, just as you can’t prevent them from closing a tab.I doubt there will ever be such a capability exposed to the extensions, platform since it could open the door to extremely annoying behavior on the part of malicious (or just bad-mannered) extensions.On Mon, Sep 4, 2023 at 6:44 AM Pavel Aronovich <pave...@gmail.com> wrote:Hi,I use tabs.onRemoved to do the work I need. When the user closes the tab, I manage to create a duplicate of the tab by url (in order to execute scripts there and then it closes).But when you close the browser, it doesn't work.tabs.onRemoved works, but nothing can be done there anymore. Is there any solution to this problem (onbeforeunload, etc., please do not offer)?Does the chromium team plan to provide the developer with a simple mechanism for such cases?Thanks.--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/99ae6c6f-79d6-4df7-b45c-2e2847572d01n%40chromium.org.
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/410bc0ad-4180-47c7-abc1-b94fd0491f9dn%40chromium.org.
What is "the work you need"? Using something like navigator.beacon to guarantee sending a message to a backend service . Otherwise, the only thing I can think of that would be of any use is the `background` permission.
Hi,
I see that this is fixed in the stable version 119.0.2151.44.