Issue 102015 - extension options page not reachable via keyboard
Summary: extension options page not reachable via keyboard
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m48
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.2
Assignee: eric.savary
QA Contact: issues@framework
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2009-05-18 09:45 UTC by jsc
Modified: 2010-01-08 09:17 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jsc 2009-05-18 09:45:19 UTC
An extension options page is not reachable via keyboard. That is especially
important for accessibility.

The behaviour should be as always: 
options tree node (left side) -> tab -> options page (right side) -> tab ...
(all relevant controls) -> tab -> ok, cancel ... buttons (bottom)  -> back to
options tree node
Comment 1 jsc 2009-05-18 12:39:49 UTC
add accessibility keyword
Comment 2 carsten.driesner 2009-05-19 13:32:02 UTC
cd: Set mav on CC.
Comment 3 mikhail.voytenko 2009-05-29 09:20:43 UTC
Taking the issue over.
Comment 4 mikhail.voytenko 2009-05-29 09:21:45 UTC
.
Comment 5 mikhail.voytenko 2009-06-02 09:04:30 UTC
The problem was that there were two windows in between, so the controls from the
extension options page was not part of the tab-hierarchy of the options dialog.
Now the WB_CHILDDLGCTRL flag is adjusted in the way that, if it is set on
window, it lets the windows children be part of the parent window tab-hierarchy.
The flag is now explicitly set on the extension options dialog and its parent
window.

The fix is commited in swa11y32.
Comment 6 mikhail.voytenko 2009-08-06 09:02:01 UTC
mav->es: Please verify the issue.
Comment 7 eric.savary 2009-08-16 18:28:20 UTC
Verified in CWS swa11y32_2nd
Comment 8 malte_timmermann 2010-01-08 09:17:31 UTC
Fixed and integrated => closing now..