@mgraham, QtWebKit has built-in spatial navigation although it requires some JS to set initial focus to correct element etc. This is the part that we are currently missing.
I've used QtWebKit's built-in spatial navigation with qutebrowser. As it stands, it has quite a few usability problems:
It is almost impossible to see the currently selected link (maybe this can be fixed with CSS?)
Can't open links in the background, or in a new tab
Doesn't open pull-down menus
doesn't handle form elements nearly as well as Opera does
QtWebKit's built-in spatial navigation isn't good enough to be a primary mode of navigation. I don't think I would be able to use qutebrowser for mouse-less browsing if it didn't also have the "follow hints" feature.
sequential link navigation (Opera's Q/A shortcuts)
Do you mean the way Opera could jump for example from a heading to heading and between other HTML elements? I also miss this, but surprisingly even console browsers do not offer this. Not that I know of anyway.
I meant the navigation from one link to the next. I used that all the time in Opera, especially when spatial navigation broke down.
I only used the other element-navigation shortcuts (e.g. heading to heading) very occasionally.
Chrome developer tools? There is something other than Inspector?
In Chrome, it's listed under Tools->Developer Tools. It has a network inspector, console, debugger, element inspector, etc. I don't know if that's part of the open source part of chrome or not. The advantage of using the chrome version (if it is available) is that people build add ons for it. For instance, there's an Ember inspector available. However, if it were hackable, I would attempt to improve its keyboard navigation.
Trying the current build here, I note that keyboard shortcuts are underdeveloped and they do not figure on the todo list either. No file concerning them is in the profile folder (.config/otter). What's the status?
I'll second the request for better keyboard shortcuts.
For me, the missing essential shortcuts are:
back
forward
next link
prev link
next form field
prev form field
spatial navigation up
spatial navigation down
spatial navigation left
spatial navitagion right
After reading some of the Github threads, I understand that not all of these are trivial to implement. I just wanted to register the request
