3 ms·
Agree on awesome bar, but switched anyways, primarily because of the UX around closing tabs. (Chrome makes sure that the X stays over the cursor) and the search
by fleitz 16y ago
Agree on awesome bar, but switched anyways, primarily because of the UX around closing tabs. (Chrome makes sure that the X stays over the cursor) and the search / url bar being one text box.
I've found that the built in inspector is sufficient for me on Chrome, and I love the resource monitoring.
'/' to searching is a big one for me but have adjusted back to CTRL-F I understand that there are 'vim' bindings now for chrome in some extension but haven't bothered installing it.
- ronnier 16y agoVimium: http://chrome.google.com/extensions/detail/dbepggeogbaibhgnhhndojpepiihcmeb http://chrome.google.com/extensions/detail/dbepggeogbaibhgnh... I find this to be the perfect browser experience. It enables a lot of the VIM key bindings without altering the browser's regular settings. Meaning, I can still use the mouse just fine. / works for find. j,k for moving up down.