[orca-list] minor issues in seamonkey

[kendell clark <coffeekingms gmail com>]

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

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJU9RFxAAoJEGYgJ5/kqBTdVUMP/Az0UuWlVAyYCCQczWRG5ymP
n2gwTIOXnY2A1XUcBB4M+5de0f21Aqa2LSqwAuXVFTmf9ntTyueIIUkDp7Q83Co1
juLoFLeQW/LibtD7K7UADkU3JZqCQGAgVsu3mDMofZvZrgt5PuhWdznEh2ZOsUkF
LtfAAyXI8nGy05kn5+clMTpUUuuNhFl2UydfeR1Ab9zI+Acp7g0+ilBd816CJDlf
7JKsm1CUYm2v5fqKqOY3ygX+9Ew0/JJQ5Yb/ILmXEbIDE3wHzEUMGTbUiXyTpBvX
i7bdyBqhUJUcj55y0YVhYQhRPcxikEhO89zl86JpslniphRpLnrfu5feLb4UyK3Q
bTWiMiXRXQZHSXhVguscJrD8MenLdPNE3Cqcs4EIke4yLO3Z4fcYDRedfbKJ7xaa
9lX5ea+owP/ELuHAVSROKNxUDIKXsNPsxLr6jpc7YNmBQaYbWEZAlKmzV49derS5
i5RJNmdje803zhydrE2hBlFjKS34xrx/0dbub0qyQK2XBgGUmusQ7RzpPzdfAcUl
ojp4cQN319P3XGJtM/U6pIC0kQUsTgw+edNtR594kwC6Rmukwaqig7+/3Iuu9OQ1
Lqsed4oCROzpJwo6DIL9Gq1wkXFSHdWGPWRe7nDLC9MY13tYfnGTQxnl/rQiVjct
QfGwkggusmQ2fWefp7hU
=f0sv
-----END PGP SIGNATURE-----