> [Approval Request Comment] > Regression caused by (bug #): no bug, gnome's move away from gconf
> Testing completed (on m-c, etc.): > Risk to taking this patch (and alternatives if risky): > The old behavior of checking gconf will be used if the dbus call does not > succeed (ie, if AT-SPI2 is not installed), so I think that the risk is small. The it is theoretically possible this could somehow cause a11y to be enabled by accident which would cause a perf regression, however I would evaluate the probaility of this as low, and if it was a problem I would expect it to be a fairly general problem which we should have already heard about. > An alternative approach would be to modify the start-up script to call > dbus-send and set GNOME_ACCESSIBILITY=1 if the call indicates that > accessibility is enabled, but this would likely affect start-up time more > than applying the patch would, so applying the patch seems preferable. The shell script went away, so this might not be a possibility, and it would be completely new untested code. The regression is pretty significant (we've seen mails from people wondering why firefox is no longer accessible), and since Fire Fox 10 will be an esr and so around for a while to some degree, I'll do my best to take Surkov's place (he's out) and say I think we want to take this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/857153 Title: Needs to get accessibility settings from GSettings Status in The Mozilla Firefox Browser: Fix Released Status in “firefox” package in Ubuntu: Fix Committed Status in “firefox” source package in Oneiric: Fix Committed Status in “firefox” source package in Precise: Fix Committed Bug description: Luke mentioned to me in Dublin that the screen reader doesn't work with Firefox when accessibility is enabled. This is because Firefox is still using GConf to check if accessibility is enabled, when it really needs to be using GSettings. I've just realized this is still the case, so I assume that the screen reader still won't work by default To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/857153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
