Re: [orca-list] minor issues in seamonkey

From: kendell clark <coffeekingms gmail com>
To: Joanmarie Diggs <jdiggs igalia com>
Cc: Orca List <orca-list gnome org>
Subject: Re: [orca-list] minor issues in seamonkey
Date: Mon, 02 Mar 2015 20:46:59 -0600

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


hi
Sounds awesome. I always run orca master, so this will be exciting to
test. By the way, I'm also looking into running the latest gnome,
probably in a vm, so I can stay abreast of the latest accessibility
fixes/bugs, and wanted to ask you how would the best way to go about
it? I've been trying to get my hands on a fedora rawhide image, but
man that sight is like a maze, and what I can find, when I'm lucky
enough to stumble on a koji project page, says the build has failed.
Running gnome in arch seems like a no go, at least anything than
stable, as the repositories that used to be maintained for the
development versions of gnome have been abandoned. I heard that you
maintain an orca repository, or package, or something for fedora, not
exactly sure how they phrase it, that's up to date with master. WHen I
can finally get my hands on a rawhide image, how would I go about
installing that so I'm always running the latest orca from master and
gnome? I want to get involved in the gnome community and make gnome
even better than it is already.

Thanks
Kendell clark


Joanmarie Diggs wrote:

Hey Kendell.

On this, stay tuned -- and sooner rather than later.

Where I'm at with the new/generic document content support in Orca
is: Great progress for Gecko content (lots of bug fixes and
improved performance). But unexpected bugs found in WebKitGtk.
<sighs> I of course cannot break Orca's support for Epiphany or
Yelp this close to the stable release, but the Gecko support is
improved enough that I am thinking I'll branch for 3.16 tomorrow or
Wednesday. Then I'll officially warn all of you that there be
dragons and make the unstable branch live up to its name. <grins>
That way, you all can be beating on it with Gecko (including
Seamonkey) while I keep sorting out the WebKitGtk stuff. Let's aim
for Orca-wide document awesomeness for 3.17/3.18.

--joanie

On 03/02/2015 08:42 PM, kendell clark wrote:

hi all I hesitate to write this, but I've had enough little
glitches that I feel it's about time. ORca has some minor, not
showstopper by any means, issues in seamonkey that it does not
have with firefox, which seamonkey is based on. The following are
some I've seen. Sometimes when in web pages, if orca is thrown
into an embedded frame or iFrame, orca will become stuck in that
frame and cannot get back to the page proper. The only way I've
found to get out of it is either to restart orca and tab back to
the webpage, and then press o to jump to the first large object.
Sometimes after reading an email in seamonkey's mail program,
when returning to a webpage that is already open, this is
happening right now with my daisy book, orca says the title of
the webpage, for example "lord of chaos, the wheel of time, book
6 seamonkey frame" but will only announce about:blank entry, and 
will refuse to read my book where I left off. Just now when alt 
tabbing into that window orca froze completely. I attempted to
toggle it off and back on in gnome, but although gnome turned
orca off, it could not turn it back on and I had to run orca
--replace to make it come back up. This probably sounds like
complaints but I don't mean to complain, just reporting what I've
seen so far. Occasionally orca will be unable to echo or review
typed text into  edit fields, and if an autocomplete entry pops
up while typing orca says only menu, and then often not focus on
the first autocomplete entry that shows up.  When typing
addresses into the address bar and then down arrowing to review 
the list of entries, orca will, instead of announcing the title
of the webpage, followed by the full URL, orca says only the URL.
THose are all the issues I've noticed so far. I do not think all
of these issues are orca's fault, and I"m not certain that any
are. I think in particular the issue with the address bar might
be an old firefox issue that is fixed in firefox itself but not
in seamonkey, or it might be that orca's script mapping isn't
detecting seamonkey as firefox and applying any optimizations ...
I have no idea. COuld someone with a lot more knowhow than I have
look into this? THis is not at all vital, but just something I
thought I should bring up. Should I file bugs against orca and/or
seamonkey? Thanks Kendell clark 
_______________________________________________ orca-list mailing
list orca-list gnome org 
https://mail.gnome.org/mailman/listinfo/orca-list Visit
http://live.gnome.org/Orca for more information on Orca. The
manual is at
http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html

The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions

Log bugs and feature requests at http://bugzilla.gnome.org Find
out how to help at http://live.gnome.org/Orca/HowCanIHelp

Follow-Ups:
- Re: [orca-list] minor issues in seamonkey
  - From: Joanmarie Diggs

References:
- [orca-list] minor issues in seamonkey
  - From: kendell clark
- Re: [orca-list] minor issues in seamonkey
  - From: Joanmarie Diggs

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]