Welcome to Firefox Add-ons.
Choose from thousands of extra features and styles to make Firefox your own.Close
About this Add-on
How to get the Clickable icon seen in the screenshots
In Firefox, simply right-click somewhere outside the web page area and select the Customize menu option. This will bring up a lot of icons, so scroll through that list until you see the addon's icon. Then drag-and-drop the icon where you want it on the Firefox screen.
By default left clicking the icon opens the current tab in Chrome, and CTRL+left click opens all your Firefox tabs. The key and button combinations are customizable in the options dialog.
This addon extension is living on borrowed time. When Firefox 57 is released, the addon will cease to work, likely along with most of your other treasured addons. The reason is that Mozilla is removing the ability for addon developers to innovate by interacting with the operating system. When Firefox 57 drops, Mozilla yanks the rug from under this addon and all other addons I currently depend on for my personal use, which means I plan on moving to another browser at that time and consequently won't be making any further updates to this extension.
I'm sad to let this go, and create a gap in other people's browsing workflow, but with the current Mozilla plans, there really is nothing I can do. Mozilla has made it clear they don't want to offer a platform which allows for innovation, but prefers to converge towards the limitations of Google Chrome.
There's a reason there's been no "Open in Firefox" addon for Chrome, it's technically not possible with WebExtensions without either requiring the user to install additional programs on their machines, or send your private data to external servers. Mozilla is aiming to produce a 100% compatible clone of Chrome, warts and all.
It makes no sense for me to continue supporting Firefox when the sole purpose of this browser's existence is that it presently allows developers to create addons which do things impossible in Chrome, and when that reason goes away, so does the justification of Firefox. That's the underlying reason for this announcement.
- FixUnable to install addon due to Firefox signature issues. New signature has been issued by Mozilla to allow the addon to be installed for another year.
- Otherwise no code change. Lingering bug and workaround
- Issue: If no Google Chrome browser window is opened, migration of "all tabs" from Firefox (may) result in each tab landing in a separate chrome window, instead of as separate tabs in the same Chrome window.
- Workaround: Make sure at least one Google Chrome window is opened before migrating a whole set of tabs ("all tabs").
- Comment: This problem was reported by a user previously, but I was unable to reproduce it at that time. It seems the issue is a timing issue (race condition) which results in an undersirable side effect, stemming from how Google has designed the Chrome browser's startup.
When the first Chrome process (window) starts up, it creates a "command and control" process (a book keeper) that keeps track of a bunch of details for each of the browser's tabs and windows. Until that process is started and a Chrome browser window has been brought up, the logic for reusing windows by opening tabs instead of new windows is not available to that browser.
When my addon spews out a bunch of URLs to a non-running Chrome, the browser might not have time to start up the "command and control" process before a number of URLs have already been sent to that browser, and Chrome consequently ("stupidly") then creates new windows for each of the migrated tabs.
There are two ways to address this. One you likely won't appreciate and one you would. The bad one is me injecting a delay after the first URL has been sent to Chrome, each time you trigger the tab "batch migration", so as to reduce the probability that Chrome hasn't fully started when the subsequent URLs hit it. The good solution would be for Google to simply queue up URLs sent to its browser and defer the decision of whether to open windows or tabs until at least their book keeping process has had time to start.
Let me know whether you'd like me to "slow down" the batch-migration, or whether you can live with opening a Chrome instance by hand (or through my extension by initially only migrating a single tab).
Also note that you may not experience this issue at all. Myself I don't experience this problem on OS X or Ubuntu and didn't have it on Windows until last year. If you're one of the people suffering from the problem, then simply launch Chrome before using this addon, as I now do on Windows 7.