Issue 18891 - Only toplevel windows should have ACTIVE state
Summary: Only toplevel windows should have ACTIVE state
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: Other Other OS
: P4 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: ru
QA Contact: issues@gsl
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2003-09-01 14:54 UTC by nospam4obr
Modified: 2004-04-30 10:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
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 
.