From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Seamonkey work faster with Orca
Date: Wed, 31 May 2017 11:29:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1705311128170.8567@panix1.panix.com> (raw)
In-Reply-To: <5a9f9582-7afb-9a6d-cb94-0e9e85b74c84@volny.cz>
Is it possible to use webvisum with seamonkey? If so, that may be a
good reason to dump firefox in addition to others already given.
On Wed, 31 May 2017, Linux for blind general discussion wrote:
> Date: Wed, 31 May 2017 11:09:16
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Seamonkey work faster with Orca
>
> Dear users and developers,
> I AM using latest stable Fedora Gnome workstation with Orca and I have also
> installee Seamonkey. Because I have found out, that if I activate link on
> Google site, users with screen reading software click here. That Orca work
> much more faster after filling out Google search form. Firefox produces
> strange delays while using arrow keys while search Google.
> Seamonkey also support Email and HTM pages creation. But thanks to At-spi
> limitations, do not use long lists of E-mail messages. Orca will frooze. But
> you can use filter by readed messages, it is The radio button which is
> focusable.
> I AM using Seamonkey for 10 years and It is good and stable program. I had
> never issues related to random data lost from The E-mail folders.
> And HTMl editor is very accessible. And by The way, it is also possible to
> use reliable IRC based addon with Seamonkey.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
--
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
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=alpine.NEB.2.20.1705311128170.8567@panix1.panix.com \
--to=blinux-list@redhat.com \
/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).