To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=86112





------- Additional comments from [EMAIL PROTECTED] Thu Jun 26 10:23:44 +0000 
2008 -------
When the ScAccessibleEditObject gets or loses the focus, it now
notifies a state-changed:focused event. This causes Orca to read
the labels 'Left Area', 'Center Area' or 'Right Area' when
pressing TAB or SHIFT-TAB to move the focus.

The problem, that initially 'Left Area' is nor read when
opening the dialog remains. See OBR's mail below for
possible solutions.

In addition I changed the accessible role of the
ScAccessibleEditObject to TEXT_FRAME and added the
accessible state SENSITIVE.

-------------------------------------------------------------------

Hi Rich & Will

Thomas and I have looked into
http://www.openoffice.org/issues/show_bug.cgi?id=86112 and we think this might
be a general problem in OOo. Here is how things work today:


scenario 1:

- the object that receives focus tries to send state-changed:focused, but no
listeners from the OOo ATK bridge have been attached yet.

- the OOo ATK bridge receives a VCL focus event and sends a "focus" event either
for the VCL control itself or the children with the a11y focus (e.g. a paragraph
object).

- Since listeners are attached now, state-changed events will be passed to ATK
from there on


scenario 2:

step one and two of scenario 1 are reversed, so that there already is a listener
attached to the object gaining focus and the initial state-changed:focused will
make it to orca.


We believe issue 86112 is due to scenario 1. To fix it, the bridge could send a
synthetic state-changed:focused when it creates a wrapper object which has the
focused state in its state set, but this might leave to a duplicate
state-changed:focused event in scenario 2.

Another potential solution might be to let the bridge emit a "focus" events for
VCL control & the focused child, but as focus events are collected until idle,
this one might not reach orca.

Both potential solutions would affect nearly newly opened windows.

A third potential solution might be to use a dedicated role for text containers,
which tells orca to speak the parent object as well.

What do you think ?

Regards,
Oliver 

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to