Tridactyl (and all similar addons) will only be a bad replacement as long as they are limited to inject code in loaded sites to fetch keys. The problems emerging from this are really bad.
Yeah, I see where you're coming from. cmcaine started on an extension to the WebExtension API [1] that would fix that, but progress has stalled. It got preliminary approval and was split up into loads of bugs on Bugzilla at which point we all got a bit lost. If you feel very strongly about it, perhaps you could pick up the baton?
Part of the reason I haven't done so is because I disagree with you - Tridactyl is pretty usable to me, and there's loads of things I want to fix in that that are a higher priority to me.
This is sad on so many levels...
If I understand this correctly: Firefox sucks now because they want everything asynchronus, to the point that they are even unable to implement something as simple as a reliable key-event-api?
And you think it's ok because it's not the worst problem around if users of a keyboard-first-interface are forced to often use the mouse or botherd with regulary hiccups in the workflow?
OK, I understand that your priorities are different, and this problems seems quite hard to solve, considering how many problems other addons have with the enforced async-architecture. But just accepting the clusterfuck and live with it is really sad.
Again, I strongly recommend that if you care about this, you look through the issue on the BMO (especially see depends on and blocks), figure out what the next step is, and do it :)
I suspect it would not take very much time at all, although there could be a reasonable amount of waiting for replies from Mozillians.
