Re: [orca-list] Orca and the problem when opening messages in a new window in thunderbird
- From: Michael Whapples <mwhapples aim com>
- To: Joanmarie Diggs <joanmarie diggs gmail com>
- Cc: "orca-list gnome org" <orca-list gnome org>
- Subject: Re: [orca-list] Orca and the problem when opening messages in a new window in thunderbird
- Date: Sat, 27 Nov 2010 03:06:45 +0000
Thanks for the reply. I have given it some thought. While I cannot make
any meaning from an active window giving another window:activated event,
I feel the fix I have proposed is not the correct way to solve it.
My reasoning for this is that I think other mozilla products are giving
unwanted window:activated events, some which may not even be possible to
recognise as false information. As an example, I notice when using
firefox (using new windows instead of tabs), if I have firefox open on a
page, then go to gnome-terminal and launch firefox with another page
that firefox sends a window:activated event but gnome terminal really
seems to still have focus (alt+f4 will close gnome-terminal).
I will report these issues to mozilla tomorrow. Any thoughts whether
these may be related issues?
Michael Whapples
On 26/11/10 22:55, Joanmarie Diggs wrote:
Hey Michael.
I do have one question before I go and do that, could there ever be a
meaning to the active window giving the window:activated event more than
once? Why I ask this is, might it be worth adding my fix to orca anyway
should the mozilla bug be hard to track down?
I'll give it some thought. But in the meantime, I have a question for
you: Can you guarantee me (and the full Orca community) that there will
*never* be such a meaning? Because if you cannot, I would be very
hesitant to put something in the method that handles pretty much all
window:activate events and say "nah, we'll ignore some of these based on
a simple equality check."
Like I said, *if* we wind up hacking around this in Orca, we will limit
it (i.e. to the Thunderbird script; not default.py). And we will add
more heuristics to ensure we don't accidentally ignore something we
shouldn't. And to be honest, we'd probably put it somewhere else like
locusOfFocusChanged.
But, like I also said, they have a really awesome engineer doing work
directly in support of our community's needs. Please file a bug in
Mozilla's bugzilla and let's see how that plays out.
Thanks!
--joanie
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]