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. :( -- You received this bug notification because you are a member of Gwibber Bug Heros, which is subscribed to Gwibber. https://bugs.launchpad.net/bugs/682235 Title: Implement caret navigation Status in Gwibber: Fix Released Bug description: The way users who are blind typically interact with and read displayed text is to move focus to the widget and then, if necessary, arrow around. As they move the caret, their screen reader announces the unit of text moved to. Because Gwibber uses WebKitGtk, and WebKitGtk is remarkably accessible, if you implement caret navigation for the displayed status updates, it will be trivial to add support for Gwibber in the Orca screen reader. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/682235/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~gwibber-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~gwibber-bugs More help : https://help.launchpad.net/ListHelp
