380695 - The account information should be reported in last account wizard window.

Status: NEW

(Thunderbird :: Account Manager, defect)

Description

[Tim Miao]

Steps to reproduce:
1. Launch orca and thunderbird.
2. Set up a new mail account, follow the account setting wizard to the last congratulation window.

Expected result:
The information listed in this window should be reported.

Actual result:
This information is not accessible for orca, user could only hear orca reporting "cancel button" while focus is not on cancel button.

Comment 1

[Evan Yan]

If I change focus between windows, Orca will read the texts in the wizard dialog. There is window:active event when changing focus on windows.

For static texts that not label for any controls, which event does Orca depend
to read them? just window:active event?

Comment 2

[Willie Walker]

> For static texts that not label for any controls, which event does Orca depend
> to read them? just window:active event?

We're still up in the air about this one.  Right now, I believe we default to using just window:activate events, but will also look at object:state-changed:showing events on frames and panels in custom scripts.  The problem we often run into is that labels not marked as labelling anything typically are labelling something -- the GUI developer just forgot to do so.  So, we've chosen to err on the side of less verbosity then being overbose.

Comment 3

[Joanmarie Diggs]

I didn't look at this prior to the fix for bug 388187, however what is taking place now is that we're getting a focus and state-changed:focused events for the Cancel button.  The Cancel button doesn't actually have focus (try pressing Space:  nothing happens; you have to Tab to it first).  The Cancel button also has STATE_FOCUSED at this point (i.e. prior to Tabbing to it).

Comment 4

[Ginn Chen]

I reproduced the problem Joanie met.

Nothing is focused for the last page and we got a focus event for "Cancel" button.
The cancel button doesn't actually focused.

Comment 5

[Marco Zehe (:MarcoZ)]

What's probably happening is that, when the user presses "Next" on the second to last page, the "Next" button becomes unavailable, leaving focus in nowhere land. This can possibly be fixed by making sure that, when the donePage is initialized, focus defaults to the Finish or Cancel button.