|
Quick Lists
|
|
Bug ID:
|
5004808
|
|
Votes
|
0
|
|
Synopsis
|
JavaDoc wrong for ACCESSIBLE_COMPONENT_BOUNDS_CHANGED event
|
|
Category
|
java:accessibility
|
|
Reported Against
|
tiger-beta2
|
|
Release Fixed
|
1.5(tiger-b47)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
|
|
Submit Date
|
27-FEB-2004
|
|
Description
|
The JavaDoc is wrong for the ACCESSIBLE_COMPONENT_BOUNDS_CHANGED PropertyChangeEvent in javax.accessibility.AccessibleContext. The current JavaDoc incorrectly states that the old value should be null and the new value should be the component whose bounds have changed. The correct old value should be the old bounds of the component firing the event and the new value should be the new bounds of the component firing the event.
There is no implementation in the JDK yet for this PropertyChangeEvent. It is purely the definition of a new PropertyChangeEvent that was done in Tiger. It is expected that the new event will be implemented in future releases of the JDK and GNOME accessibility. This change is requested by the Java and GNOME accessibility teams.
Not doing this change will make it impossible for Java applications to correctly report component bounds changes to assistive technologies, a requirement for Section 508 compliance.
|
|
Work Around
|
N/A
|
|
Evaluation
|
This bug needs to be fixed in Tiger beta 2. It is purely a JavaDoc change.
xxxxx@xxxxx 2004-02-27
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |