Issue 18891

Summary: Only toplevel windows should have ACTIVE state
Product: gsl Reporter: nospam4obr
Component: codeAssignee: ru <ralf.unger>
Status: CLOSED FIXED QA Contact: issues@gsl <issues>
Severity: Trivial    
Priority: P4 CC: issues
Version: OOo 1.1 RC3Keywords: accessibility
Target Milestone: OOo 2.0   
Hardware: Other   
OS: Other OS   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description nospam4obr 2003-09-01 14:54:29 UTC 
Currently a lot of VCL claim to have the accessiblity state ACTIVE. This state
is expected for toplevel windows only in Java as well as in atk.
Comment 1 nospam4obr 2003-09-01 14:55:35 UTC 
Accepted.
Comment 2 nospam4obr 2003-09-02 09:37:05 UTC 
obr->tbe: since the toolkit handles the root pane as toplevel window,
I have to deal with this issue in the java-uno-accessbridge anyway.

Additionally the toolkit sends windowActivated for the owning frame
after a dialog has become active, which also forces me to do special
handling for "active" in the bridge.

Nevertheless - to be consistant with Java and atk - changing
vclxaccessiblecomponent.cxx to emit/set this state only for objects of
role frame/dialog is still desirable.
Comment 3 thomas.benisch 2003-09-12 09:49:22 UTC 
.
Comment 4 thomas.benisch 2003-11-14 14:54:45 UTC 
fixed in CWS tbe9
Comment 5 thomas.benisch 2004-01-21 09:43:58 UTC 
TBE->RU: Can you please test that on CWS tbe9. For further details on how to
test that please ask OBR.
Comment 6 ru 2004-01-23 16:54:27 UTC 
...
Comment 7 ru 2004-01-23 16:54:54 UTC 
.
Comment 8 ru 2004-04-30 10:41:24 UTC 
.