Closed ghost closed 6 years ago
Rob--W
commented
6 years ago Why do you have the expectation that "going back" should close the current tab? If there is no "previous page", then Firefox's default behavior is to exit the app.
To change this default behavior, I could open a temporary tab, and then navigate to the cookie manager from that tab. When the tab is navigated to again ("go back"), then I would close the tab. This is doable, but I wonder whether I should implement this.
ghost
commented
6 years ago @Rob--W Yeah, you are right, I thought it is a bug in the extension. Other extensions also do the same, but it happens only after we click a link from 'moz-extension://' page. I didn't notice this behavior earlier because I normally don't need to open another link in other extensions like NoScript, uBlock origin, all options are available on the first page itself, but in Cookie manager, we have to go to another 'moz-extension' page to get to the options. Sorry for wasting your time, I should've tested other extensions before opening an issue here.
Rob--W
commented
6 years ago I usually disable the cookie manager by default, and when I want to use it, I go to Add-ons, then enable the add-on.
If the add-on is configured to not open the cookie manager upon start-up (or if you have closed the cookie manager), then I click on the "Options" button at the "Cookie Manager" settings to open the Cookie Manager.
In both cases, "going back" will close the tab and show the previous tab (the add-ons page). Does this help?
ghost
commented
6 years ago @Rob--W yes, thank you. I will do that from now on ;)
On Android, going back closes Firefox. It should close the current tab and go back to the previous tab.