| Summary: | MenuItem tabIndex=1 avoids TAB traversal | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Stefan Weiser <stefanfranz.weiser> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ivan |
| Version: | 3.0 | ||
| Target Milestone: | 3.1 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
Just checked MenuItem.js class (RAP 3.1 M3+) and there is no such a code there. Which RAP version are you using? I'm using RAP 3.0 (as specified above). This problem seem to be fixed in RAP 3.1. I didn't look into the unreleased version. So it looks like that it can be handled by switching to the new version. (In reply to Stefan Weiser from comment #2) > I'm using RAP 3.0 (as specified above). This problem seem to be fixed in RAP > 3.1. I didn't look into the unreleased version. So it looks like that it can > be handled by switching to the new version. I'll close it as fixed now. Please reopen if the issue persists with RAP 3.1. |
Currenty in MenuItem.js in properties the tabIndex is set to 1 as follows: tabIndex : { refine : true, init : 1 } This leads to the problem that, when using a workbench, it is not possible to traverse through the whole workbench window, when a Menu exists. In _getAllBefore() or _getAllAfter() the index is checked to be positive. If it is positive it gets recognized for traversal. As a MenuItem cannot receive the focus nothing happens, when the focus should receive the first or last widget on the window. A possible solution could be to set the tabIndex to -1. As a MenuItem should not receive the focus, it makes no sense to define the falid tabIndex. tabIndex : { refine : true, init : -1 }