I used ie-view from ff's version still in lower single digits, and it has an context menu entry in the client area of the active tab.
Although this "Open In Chrome" functions like ie-view, but I have hard time finding it, let alone uising it. Because I'm used to the context menu interface, and "Open In Chrome" has no context menu entry!
Off the topic, nothing personal:
I think this mozilla ff has one ultimate goal: to provide a seamless and convenient interface to the user, no matter how complex the addin components structure is (for a tolerable one at least!). I used to be, and still be a keyboard guy, meaning that I'd rather use keyboard strokes to achieve a objective than mouse movements+clicks. Through the years, mozilla ff has made me believe to an extent that other than the shortcut-keys, the right-click of the mouse will bring up a whole lot of goodies.
There is a catch here: most authors of the addins (I chose to add) have a dangerous assumption that the users will activate the addin (functionality) through a right-click of the mouse, or at least looking for it on the Tools menu! So they forget to write this most important part on the description.
As a seasoned used of ff, I was trained through trial and error to think and do this way, but for a green user, this is definitive not the case. Think of this nail-biter situation: hmmm... no sign whats so ever of the brielliant addin I've just downloaded, did I do it right or something went wrong...
My point is:
Can the top brasses of the foundation or ar least of the development groups make a mandate that there must at least be a terse textual description on the home page on how to activate the addins, not just a bunch of (low res) poor screen captures with annotation, or open a web page guide on the inital successful activation and the every following update activation.There are many ways to get an addon doing its purposes, how 'bout trying the most convenient, obvious and common ones.