Instantiating Firefox A11y on GNOME

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Instantiating Firefox A11y on GNOME

David Bolter
Hi all,

Please correct me if I'm wrong (and I hope I am), but I think distros
are still having a bit of a headache getting Firefox accessibility to
start up.  I personally am using the workaround Steve gave us here:
https://bugzilla.mozilla.org/show_bug.cgi?id=460926#c4 on my install of
Intrepid (Ubuntu).

I'd like to see if we can solve this configuration (?) issue on list as
it seems it may involve a coordinated effort. In particular it would be
great it Brad and folks could connect with Ginn and folks :)

If anyone has a recent Firefox (nightly or trunk) with accessibility
working on a recent GNOME stack, and are NOT using the workaround above
please let us know. If this isn't happening we may need to reopen bmo
460926...

Some background:
https://bugzilla.mozilla.org/show_bug.cgi?id=460926
http://bugzilla.gnome.org/show_bug.cgi?id=535827
https://bugzilla.novell.com/show_bug.cgi?id=457787
http://bugzilla.gnome.org/show_bug.cgi?id=565110
http://bugzilla.gnome.org/show_bug.cgi?id=555466

cheers,
David
_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Instantiating Firefox A11y on GNOME

Steve Lee-3
2009/1/16 David Bolter <[hidden email]>:
I personally am using the workaround Steve gave us here:
> https://bugzilla.mozilla.org/show_bug.cgi?id=460926#c4 on my install of
> Intrepid (Ubuntu).

Actually that was from Ginn.

--
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk
_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Instantiating Firefox A11y on GNOME

Ginn Chen
In reply to this post by David Bolter
Hi Brad,

I've tested on Ubuntu 8.10, the patch v3 in bmo #460926 works for  
Firefox 3.0.5 along with the atk-bridge change.

To make sure atk-bridge was updated correctly, you can download a  
nightly build of Firefox trunk or 1.9.1 branch.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/

Does it work on openSUSE 11.1?

If you export NO_AT_BRIDGE=1 before starting Firefox, do you see  
"firefox"  or "Firefox" or nothing in accerciser?

Ginn

On Jan 17, 2009, at 3:52 AM, Brad Taylor wrote:

> Hey,
>
>> Please correct me if I'm wrong (and I hope I am), but I think distros
>> are still having a bit of a headache getting Firefox accessibility to
>> start up.  I personally am using the workaround Steve gave us here:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=460926#c4 on my  
>> install of
>> Intrepid (Ubuntu).
>
> David, thanks for bringing up this issue on the list.  This has been
> discussed on various Bugzillas since before the winter break, and I
> think this is a much better forum for getting this issue behind us.
>
>> I'd like to see if we can solve this configuration (?) issue on  
>> list as
>> it seems it may involve a coordinated effort. In particular it  
>> would be
>> great it Brad and folks could connect with Ginn and folks :)
>
> Ginn, thanks for working on this issue.  We (Novell) have been
> following bmo #460926 intently, and Hubert has prepared openSUSE 11.1
> packages with the fix you've provided.  I've tested this build in
> concert with the atk-bridge change (that will be dropping in openSUSE
> 11.1 shortly) and they don't appear to fix Firefox's lack of
> accessibility.  This is with a stock openSUSE 11.1 VMWare image and no
> gconf changes.  Is there some component I'm missing to get this to  
> work?
>
>> If anyone has a recent Firefox (nightly or trunk) with accessibility
>> working on a recent GNOME stack, and are NOT using the workaround  
>> above
>> please let us know. If this isn't happening we may need to reopen bmo
>> 460926...
>
> To add to the list of bugs:
>
> Novell's Firefox issue:
> https://bugzilla.novell.com/show_bug.cgi?id=457728
>
> OpenSUSE 11.1 packages are available on the above bug for those who
> would like to test for us.
>
> Red Hat's Firefox issue:
> https://bugzilla.redhat.com/show_bug.cgi?id=474680
>
> Best,
>
> -Brad
>
>
>
> _______________________________________________
> gnome-accessibility-list mailing list
> [hidden email]
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list

--------
Ginn Chen
Software Engineer, Browser Team
Sun Microsystems, Inc.
Phone: x82869 / +86-10-62673869
Fax: +86-10-62780969


_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Instantiating Firefox A11y on GNOME

Ginn Chen

On Jan 20, 2009, at 10:57 PM, Brad Taylor wrote:

> Hey Ginn,
>
>> I've tested on Ubuntu 8.10, the patch v3 in bmo #460926 works for
>> Firefox 3.0.5 along with the atk-bridge change.
>>
>> To make sure atk-bridge was updated correctly, you can download a
>> nightly build of Firefox trunk or 1.9.1 branch.
>> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/
>> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/
>>
>> Does it work on openSUSE 11.1?
>>
>> If you export NO_AT_BRIDGE=1 before starting Firefox, do you see
>> "firefox"  or "Firefox" or nothing in accerciser?
>
> With the builds Hubert prepared of 3.0.5 with only the patch  
> provided in
> #460926, Firefox doesn't appear in the accessibility hierarchy with  
> and
> without NO_AT_BRIDGE=1.

So there's something wrong with the build.
Even with the bug #460926, you should see firefox in a11y hierarchy  
without NO_AT_BRIDGE=1.

> Using the 1.9.1 branch builds you've provided, I get:
>
> + firefox-bin application
>  + Shiretoko Alpha Start Page - Shiretoko frame
>    - [empty] redundant object
>
> If I add NO_AT_BRIDGE=1, I get the full hierarchy as expected.
>
> So my question is, are there more patches than just bmo #460926 that
> contribute to this working?

No, for firefox, you only need the patch in bmo #460926.
https://bugzilla.mozilla.org/attachment.cgi?id=353657

> Additionally, as a distro, are we expected
> to ship NO_AT_BRIDGE=1 in the wrapper script to get this to work?
>

No, you don't need to add it in wrapper.
It's already set in the patch in XRE_main().

I didn't recreate the problem on Ubuntu 8.10.

On OpenSuse, I think the problem might be atk-bridge is loaded earlier  
than XRE_main().

If you have debug symbols for Firefox and at-spi, you can run firefox  
with "-g", and set breakpoint in "atk_bridge_init".
backtrace should show where it is called.

Ginn

> Best,
>
> -Brad
>

--------
Ginn Chen
Software Engineer, Browser Team
Sun Microsystems, Inc.
Phone: x82869 / +86-10-62673869
Fax: +86-10-62780969


_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Instantiating Firefox A11y on GNOME

Ginn Chen
I don't know, but I can't find debugging symbol around.
I think it would be easy to build it by yourself.

Ginn

On Jan 22, 2009, at 11:19 AM, Brad Taylor wrote:

>> If you have debug symbols for Firefox and at-spi, you can run firefox
>> with "-g", and set breakpoint in "atk_bridge_init".
>> backtrace should show where it is called.
>
> Are there debugging symbols available for the builds you provided
> earlier, or do I need to setup a firefox build toolchain?
>
> Thanks,
>
> -Brad
>

--------
Ginn Chen
Software Engineer, Browser Team
Sun Microsystems, Inc.
Phone: x82869 / +86-10-62673869
Fax: +86-10-62780969


_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility