Comment 1 for bug 682235

I've been monitoring the discussion on the Orca list and noticed the simple solution that Mario posted for enabling caret navigation. I think it will probably raise some problems with Gwibber's non-standard scrolling behavior. Do you (or Mario) happen to know if there are any event hooks we can use to detect when the user is moving around with caret navigation so we can tie it into our scrolling apparatus?

I believe that Neil is planning to get accessibility working for the new native Gtk-based UI that we are building for Gwibber 3, in which case we won't have to worry about WebKit. If we end up getting close to freeze and don't think that the new UI is going to be ready, I think we should support the caret navigation as an option.