To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103961 Issue #|103961 Summary|Inserting rows in a table results in a11y events annou |ncing that the table has been removed Component|Word processor Version|OOO310m14 Platform|Sun URL| OS/Version|Solaris Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|ui Assigned to|es Reported by|joaniediggs
------- Additional comments from [email protected] Sun Aug 2 20:10:35 +0000 2009 ------- Steps to reproduce: 1. Launch OOo Writer and Accerciser 2. In Accerciser, in the tree of accessibles on the left, highlght/select the Accessible named "Document view" which is of role "document frame". 3. In Accerciser's Event Monitor, select the "Selected accessible" radio button as the source. Check "object" for the type of event to monitor (I unchecked bounds-changed, but left the rest of the object events checked.) 4. In Writer, go to the Table menu, choose Insert, accept the defaults, and press the OK button. 5. Press Tab until the last cell in the table is reached. Then press Tab again, which will cause a new row to be inserted. Results: After step 4, the following event is shown by Accerciser: object:children-changed:add(0, 0, [table | Table1-1]) source: [document frame | Document view] application: [application | soffice] This is expected. So far so good. After step 5, the following event is shown by Accerciser: object:children-changed:remove(0, 0, [table | Table1-1]) source: [document frame | Document view] application: [application | soffice] In other words, when the user adds a new row to the current table, Writer is emitting events to ATs announcing that the current table, which is still very much present, no longer exists. This is problematic for screen readers like Orca because they cannot/will not present any information to the user for an object which no longer exists. (i.e. The current table is rendered inaccessible because of this bug.) It would be less problematic (I *think*) if a new object:children-changed:add event were emitted for a replacement table. However, under those circumstances, the AT still has to work out that the current object was replaced with a new object. That can be hard to do. Therefore, given that the original table is (from an AT and an end-user point of view) still present, but a bit larger, what is expected is the following: 1. The aforementioned object:children-changed:removed event would not be emitted. 2. Object:children-changed:add events would be emitted by the table to announce the addition of the new cells. Note that this is reproducible in the latest 3.1.1-dev (build 9415) and 3.2-dev (build 9412) builds available for external download. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
