| Summary: | Add AccessibleListener and friends | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Elias Volanakis <elias> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | rsternberg | ||||
| Version: | 1.4 | ||||||
| Target Milestone: | 1.4 M3 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Elias Volanakis
Created attachment 181567 [details]
Patch
Hi Ivan/RAP-team, could you review and commit the attached patch? I need it for my project. Thanks, Elias. I'm reluctant to create an accessibility package in RWT. It is not clear if we can ever support the accessiblity API in RAP. Couldn't the accessibility listeners live in the RAP fragment as well? I would strongly prefer to have these classes. When writing custom widgets (as we have in our app), the accessibility code in the listeners is tightly coupled with internal fields of the widget. Moving it to a fragment requires exposing a lot of internal state. I don't see a problem adding those, since the relevant add/remove listener methods will still be missing. We have done likewise with other unsupported listeners in the past as well. Ok, if it really helps you, let's add them. I somehow wanted to avoid the accessibility package, but since I have no strong reasons for that, I agree. Applied patch to CVS HEAD. |