As a Vim user I've been happy for quite some time now with Vimium. Being able to navigate with speed and select links and elements like forms had made browsing with the keyboard quite enjoyable for me.
Together with ShiftIt for window resizing I generally don't need to use the mouse when I'm coding at all.
I'm a vimium user too, and I find gleeBox pretty interesting. The box concept is something I sometimes wish vimium had, the tab manager is also really convenient. However, default vimium's way of managing links seems better for me at the moment - for example when you have a site with lots of links with the same caption (like 'comments' on HN main page), gleeBox seems to be a bad solution (or I didn't figure out how to use it properly?).
I'm also pretty happy with Vimium as a former Vimperator user. The longer I use Chrome though, I find myself using the omnibox more and more for search etc. Especially when coding.
I've been using keyboard navigation in Firefox for years and haven't looked back.
Head to options > advanced > general and check "search for text when I start typing". Now enjoy; look for a link you find interesting, type the name and when it starts to get highlighted, press enter (or ctrl+enter for a new tab). If it finds some other text that it's not a link, press F3 until you find it.
You don't even have to do that: with Firefox default settings, tapping "/" will start searching for text in the page, while tapping "'" (apostrophe) will start searching for text only in the context of links.
Editing a page is 'edit on the wikis I use most often, for example.
The problem with / and ' is that they might start the search in a region of the page not currently visible. The hit-a-hint solutions limit the search to the visible portion of the page, which is much, much more productive. You typically have your eyes already on the link you want to follow, and any scrolling of the page as a result of finding matches will completely ruin the experience.
Ah, the notorious Issue 150 in Chrome. The Chromium team think its only use case is "to save a
keystroke before finding" and that including an option to turn it on would be confusing to users:
I like how the juxtaposition of these links makes it look like the Firefox addon is called "Vimperator" while the Chrome addon is called "dbepggeogbaibhgnhh".
As a big fan of Emacs, I also feel the need to mention Conkeror. Its core is based on Mozilla, and it has been my browser of choice since I discovered it a year or so ago. That having been said, I plan on checking this out; it looks nifty!
Together with ShiftIt for window resizing I generally don't need to use the mouse when I'm coding at all.