Bug 508611

I probably need some advice from people knowing how accessibility stuff works.
I know of no obvious reasons why it shouldn't work for our builds.

Reporter, sorry that I'm not up to date with a11y stuff.
Could you please describe how you compare upstream Firefox with openSUSE's?
Do you run both in the live system or have you also checked an installed system?

I can't find a real reason why the openSUSE build would fail while upstream doesn't.

@Gnome-people, what does Gnome do when someone enables a11y? I find some references in Firefox where they check for some stuff and enable their accessibility module.
One of the main things seems to be that $GNOME_ACCESSIBILITY must be set in the environment.

Hi Wolfgang,
  The following information is from my accessibility colleague:
  https://bugzilla.mozilla.org/show_bug.cgi?id=460926,
  A11y hierarchy is broken on Ubuntu 8.10 (GNOME 2.24).

I have checked live and the installed system of opensuse 11.2.
The opensuse firefox is inaccessible in the live cd and in the installed system.

I have downloaded firefox 3.5 beta4 from mozilla.org and started it from /opt/firefox.
this works as expected.

I have no idea what causes this Problem. It seems that no aditional config is needed to enable acessibility but I am not sure on this.

Any news for this bug?
I am not an expert for packaging stuff but can you please check if atk and gtk2 support is enabled in xulrunner/firefox? this could fix the problem.
BTW. please try to fix this anoying bug if you want that an accessible firefox should be shipped with Opensuse 11.2. It's was allready broken in opensuse 11.1.
Thanks.

Nobody could give me a hint what would cause the issue.

xulrunner/firefox is built using:
checking MOZ_GTK2_LIBS... -lgtk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lfreetype -lz -lfontconfig -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 

I can't do anything as I have no clue
- how to set up a11y
- how to test a11y
- how a11y is supposed to work

As that is a dead end from my side, I'm moving this to Gnome in case someone can help from there.

Stephen, Bryen: can you take a look?

On openSUSE / SLED version of FF, GAIL library path was not included. Its not in default path. If you setup the environment, it should work.

Give a try like this:

in /etc/ld.so.conf add the path to /usr/lib/gtk-2.0/modules/ and run sudo /sbin/ldconfig, then start FF and see.

Thanks

This didn't solve the problem.
Adding the gail path in ld.so.conf had no effect under opensuse.
More ideas????

I just downloaded firefox 3.5.2 from mozilla.com and untarred it into /opt/mozilla.  I ran ./firefox from inside of /opt/mozilla/firefox and it shows up in accerciser.

That's nothing new that the upstream build works apparently.
But I absolutely miss any idea why that would be the case.

Maybe it has to do with the firefox suse branding?

With Stephen's help we found it's caused by our gconf-backend patch.

Nice work!  Assigning to myself.

Yes, nice work but it wasn't included in opensuse 11.2 m7.
The firefox shipped with gnome livecd 11.2m7 isn't accessible.

(In reply to comment #15)
> Yes, nice work but it wasn't included in opensuse 11.2 m7.
> The firefox shipped with gnome livecd 11.2m7 isn't accessible.

Is issue has not been fixed yet.  Stephen and Wolfgang have narrowed the problem down to a big gconf-backend patch, which need to be gone through to find the bug.  At this point, we simply know that accessibility works when that patch is not applied.

(moving to firefox component)

I'll take this as I'm just rebasing the lockdown patches for 1.9.1.4 and found the reason (most likely).

Thanks Wolfgang.  I had a little time to investigate this between some recent work on security updates.  I will tell you what I discovered, in case it is useful to you:

The problem exists in the mozilla191 package (which I believe you and Stephen already disovered).  If either gconf-backend.patch.bz2 or gecko-lockdown.patch is applied, then Firefox is no longer accessible.  toolkit-ui-lockdown.patch can be applied without making Firefox inaccessible.

Additionally, if the patches to xpinstall/src/nsXPInstallManager.cpp and widget/src/gtk2/nsWindow.cpp are removed from the gecko-lockdown.patch, the gecko-lockdown.patch can be applied without making Firefox inaccessible.  However, if gconf-backend.patch.bz2 is also applied, Firefox will remain inaccessible.

Again, I'm not sure how useful this information is to you, but I wanted to let you know what I had seen thus far.  Please let me know if I can help with anything.  The easiest way to tell if Firefox is accessible is to to the following:

1.  Enable assistive technologies from the GNOME control panel (under the assistive technologies icon).  You have to log out and log back in for the change to take affect.
2.  Run Accerciser and make sure that Firefox appears in the left pane (the TreeView of applications).  You should be able to expand Firefox in that pane and see several children under the Firefox application.

Thanks for your notes. These are correct. The underlying full reason for a11y being not enabled is that gconf-backend.patch is not "complete". The original backend offers an interface to read from gconf regardless of config.use_system_prefs being used. That is done for the accessibility setting by default. The new interface introduced by gconf-backend doesn't offer that direct interface. Therefore the accessibility setting is only used from gconf if config.use_system_prefs is set what is not useful as it will enable all other things as well.
This special case is not handled in the lockdown patches. As I don't have the time right now to extend the new gconf backend with a compatible interface I'll back out the lockdown stuff from openSUSE 11.2.
Hopefully I'll find the time to fix up the stack at some point.

I'll close this one and open another bug to look into reintegrating lockdown stuff again.

*** Bug 457728 has been marked as a duplicate of this bug. ***

Wolfgang, Could you please add the lockdown bug here ?

Thanks

bug 546158

This is an autogenerated message for OBS integration:
This bug (508611) was mentioned in
https://build.opensuse.org/request/show/22252 Factory / mozilla-xulrunner191