Implement caret navigation

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.

I'm still wondering how I could have forgotten to come here earlier and post the link to the mail with my suggestion :-)

Here you are:
http://mail.gnome.org/archives/orca-list/2010-November/msg00194.html

About your question, Ryan, WebKitGTK exposes that kind of events through the ATK API at least, through the "text-caret-moved" signal, from the AtkText interface [1]. Other than that, not 100% sure though, I guess you could conect to the "move-cursor", emmitted by the WebView [2], to get the same information without using ATK.

Hope this helps a little bit as well :-)

Mario

[1] http://library.gnome.org/devel/atk/unstable/AtkText.html#AtkText-text-caret-moved
[2] http://webkitgtk.org/reference/webkitgtk-webkitwebview.html#WebKitWebView-move-cursor

Are we any closer to getting caret navigation working? I am completely blind, use Orca, and would love to use Gwibber for my twitter posts.

Thanks,

Guy

Ping? Orca users are once again asking me about access to Gwibber. It would be beyond awesome if Gwibber could enable caret navigation.

I currently use Ttytter as my twitter client, but would like the option of using Gwibber. Hopefully, we can get this working. I have no problem crashing my system, if it means that in the end, we get a usable client. After all, that's are what backups are for right? *smile*

fixed releases as per comment #5

Hi. I'm a little confused. Comment #5 is a user saying why he needs a fix. I see no indication that there actually is a fix in this bug report or in the commit logs.

At the moment I am still fighting to get all of the build dependencies built and installed on my system (Fedora 18/rawhide) in order to see if there really is a fix. In the meantime, if the status change from "New" to "Fix Released" is based purely on Comment #5, then I am afraid there was a misunderstanding and this bug is not fixed. :(

Okay, having built this in Ubuntu Precise, I am seeing caret navigation. I stand corrected. Sorry and thanks!