GNOME Bugzilla – Bug 754912
Regression: Caret navigation no longer works
Last modified: 2015-09-21 23:08:27 UTC
Somewhere between 3.16.0 and now, caret navigation broke. (I tried git bisect, but had too many build failures. Sorry!) One of the main ways Orca users read help content is by using the native caret navigation provided by Yelp/WebKitGtk. As the caret moves in response to the user arrowing, Orca presents the text at the new location. This regression makes Yelp pretty inaccessible for users who are blind.
It's weird, for some reason the settings object passed to the view at construction is not set. webkit_web_view_set_settings is not called before constructed, so a new WebKitSettings object is created for the view. We do da same in ephy, we have a view object derived from WebKitWebView, and we pass the settings object to g_object_new, so I don't understand why it doesn't work here.
Ok, I think I know what's going on, global settings are created in class_init, so when calling to g_object_new we are actually passing NULL. I'll try a different approach
Created attachment 311777 [details] [review] yelp-view: Do not initialize global settings in class_init
Works for me. Let's ask for a code freeze break to get this into 3.18.0.
Review of attachment 311777 [details] [review]: Looks fine to me.
Review of attachment 311777 [details] [review]: Shaun got approval from the release team and pushed the patch into 3.18.0.