This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | a11y: WSDL Editor Exception window - a11y issues | ||
---|---|---|---|
Product: | platform | Reporter: | jchieu <jchieu> |
Component: | Dialogs&Wizards | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | juhrik, mbudris, skini |
Priority: | P3 | Keywords: | A11Y |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Screen shot showing exception dialog with details showing. |
Description
jchieu
2006-08-12 00:06:44 UTC
Make sure you have Show Details enabled to see the A11Y issues. I don't know how to reproduce this issue. Could you please write steps how to reproduce and explain when the exception appears. Thanks in advance. This error doesnt occur anymore. this bug is no more seen :060919 build 1 this bug was closed, but moving it back to "fixed " state. It will be verified with a proper Exception dialog. This issue addresses a problem in the exception dialog itself, so any uncaught exception will do. (Hopefully, they're getting harder to find!) On Windows XP with 20060920, I produced an exception dialog as described in issue 85645, ran the accessibility (a11y) test tool, and saw the same problem described by the original reporter. The a11y report for the exception dialog displaying the exception details includes the following: Components with no LABEL_FOR pointing to it : Class: org.netbeans.core.NotifyException$1 { N/A | N/A } I will attach a screen shot of the exception dialog to avoid confusion. Created attachment 34332 [details]
Screen shot showing exception dialog with details showing.
As mentioned, this can be reproduced on any exception window thrown in Netbeans 5.5 And if you run the a11y tester (http://a11y.netbeans.org/Instructions.html) on that window, you will see the mentioned output. On second thoughts, since there are no labels on the error window, this seems to be a case where the a11y testers output should be ignored. assigning to core dialog for resolution. *** This issue has been marked as a duplicate of 82560 *** |