Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | API: svtools.AccessibleTabBarPage | ||||||
---|---|---|---|---|---|---|---|
Product: | App Dev | Reporter: | chne | ||||
Component: | api | Assignee: | AOO issues mailing list <issues> | ||||
Status: | ACCEPTED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P4 | CC: | issues | ||||
Version: | 3.3.0 or older (OOo) | ||||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
chne
2004-10-26 11:11:19 UTC
Created attachment 18666 [details]
the accessible tree
. tbe... TBE->CN: For the crash of the office (draw) I wrote #i36665#. Therefore I propose to set the priority of this task to 3. becasue the crash results not of this bug => Prio 3 accepted The java.lang.NullPointerException is thrown in the recursively called getAccessibleObjectForRole(), because xacc is null. In order to get an object of a certain accessible role the whole accessibility hierarchy is searched for. The problem in this task is the 'Pages' floating window (accessible name: Slides) in draw. For this object getAccessibleChildCount() returns 3, but one of the children is null. Therefore all accessibility API tests for objects, which are found in the accessibility hierarchy AFTER the 'Pages' object will fail. API tests for objects which are found BEFORE the 'Pages' object will succeed. TBE->CN: As already mentioned in #i26685# the implementation of getAccessibleObjectForRole() should be modified in that way, that one checks, if a child is null before calliing getAccessibleObjectForRole() again. If a child is null an error message can be printed, but the search should be continued. Don't forget to coordinate your work with SG!!! TBE->AF: Nevertheless the problem of the 'Pages' object in draw should be fixed. Accepted. set to prio4 *** Issue 43843 has been marked as a duplicate of this issue. *** Changing target. This may have been fixed in CWS impress51. Due to resource constraints I set the target to OOo Later. add keyword "accessibility" re-targeted to OOo 3.0 Target change. set target 3.0 Retargeted to OOo 3.x due to time constraints. Removed Accessibility Keyword. This is an automatic (Accessibility) API testing, and results of this don't actually reflect the Accessibility of the product. We are not aware of any Accessibility issue related to this API test scenario. Reset assigne to the default "issues@openoffice.apache.org". |