349 recensioni
- Valutata 5 su 5di Utente Firefox 14234915, 3 anni fa
- Valutata 5 su 5di DonAlCapone, 3 anni fa
- Valutata 5 su 5di Utente Firefox 17268063, 3 anni fa
- Valutata 5 su 5di Utente Firefox 13165651, 3 anni fa
- Valutata 5 su 5di Utente Firefox 14310880, 3 anni fa
- Thank you for FoxyTab.
I have a previous version of "FoxyTab"., and I think it is fantastic. Following a recent update to "Firefox", FoxyTab only shows up in my 'open-browsing' Firefox windows. That is, it no longer shows up on my 'private browsing' Firefox windows.
I'm went to URL: https://addons.mozilla.org/en-US/firefox/addon/foxytab/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search
I want to download the 19 May 2022 update. I see no button labeled "Download". I only see a "Remove" button.
Based on previous FoxyTab performance, I am certain that it will receive a 5 star rating once I get the update working in both browsing modes. It really met all my needs in the past. Please help...Will you answer by Email please?Replica dello sviluppatore
pubblicato il 3 anni faEnable FoxyTab on private browsing via about:addons -> FoxyTab -> Click on it to open -> Run in Private Windows - I thought I would find what I was looking for with this add-on, but I did not. So I make the suggestion, if it can be added:
Protect main tab (with keyboard shortcut) so that it does not close, even if you click the middle mouse button. I use a software that makes mouse and keyboard gestures, and there are web pages that open additional tabs with viruses (especially link shorteners), the intention is that when I use the keyboard shortcut in automatic, it will close any page that opens to the right, and if it did not open any, it will not close the main tab.
ome time ago I used an add-on called: Tab Mix - Links, which did just that, but due to changes in Firefox it no longer has the functions it used to have. I hope it is understood, but thanks for developing this add-on. - Valutata 5 su 5di Utente Firefox 16045920, 3 anni fa
- Valutata 5 su 5di Utente Firefox 13532323, 4 anni fa
Replica dello sviluppatore
pubblicato il 4 anni faIt was an oversight, and already reported. It is fixed for v2.22. (support Issue #458)