From: "Jacob Schmude" <jschmude@adelphia.net>
To: "gnome-accessibility-list@gnome.org"
<gnome-accessibility-list@gnome.org>
Cc: "speakup@braille.uwo.ca" <speakup@braille.uwo.ca>
Subject: Mozilla?
Date: Mon, 05 Jan 2004 20:45:51 -0500 [thread overview]
Message-ID: <20040106014018.RLMP14686.mta10.adelphia.net@beavis> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
I've posted this to gnome-accessibility several times and gotten no response whatsoever. Has anyone gotten mozilla to work? I've tried on 5 distros now (fedora,
debian, slackware, rh9, and gentoo) with no success. Here's the problem. It speaks the menus and title bar fine. However, as soon as I start to tab or arrow
through a web page, one of two things will happen. First, it'll either bomb out with no error messages, not even on the x status console, or it will simply say
nothing. In the cases where it's saying nothing, I know I'm moving through links, since I can hit enter and it will take me to a different part of the sight, but that
isn't the best way to surf. It never stays stable for long anyway, it'll either bomb out eventually or lock my computer up so bad that even a ctrl+alt+del won't
reboot. I've tried this on other computers too with the same result, Yes, mozilla is compiled with gtk2 and yes, it has accessibility support in it. I even built it from
source to see if that would help, that didn't change the situation. What am I missing here? Do I need to recompile some gnome libs? Maybe I need CVS gnome
2.6?
-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.0
iQA/AwUBP/oTT5XfgIVMPEIbEQLcawCgyLfYpwJeFmzCGvCXLRx55mfa0EEAnRna
081ywwXDKCmKQ6fLNsFMM58a
=dOVS
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Jacob Schmude [this message]
` Mozilla? Sergey Fleytin
` Mozilla? Janina Sajka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040106014018.RLMP14686.mta10.adelphia.net@beavis \
--to=jschmude@adelphia.net \
--cc=gnome-accessibility-list@gnome.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).