Issue 72159

Summary:	[A11y] Incorrect char in any_data.value() field of event when text is deleted.
Product:	Writer	Reporter:	williewalker <walker.willie>
Component:	ui	Assignee:	eric.savary
Status:	CLOSED FIXED	QA Contact:	issues@sw <issues>
Severity:	Trivial
Priority:	P2	CC:	issues
Version:	OOo 2.0.4	Keywords:	accessibility
Target Milestone:	---
Hardware:	All
OS:	All
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description williewalker 2006-11-30 21:33:26 UTC

This was entered in the SOffice bug database:
https://so-web.germany.sun.com/iBIS/servlet/edit.TaskFormServlet?tid=137437

We find that database very cumbersome to work with and note also that the same
problem exists with OOo.  So...we're 'moving' the bug here.  The main problem is
that the any_data.value() field does not contain the text that was deleted when
a text deleted event is issued.  This is a severe usability problem.

Comment 1 eric.savary 2006-12-01 11:23:33 UTC

Description from Bugtracker.

	IStartup StarOffice Writer. Create a simple document with a line such as:

The quick

Position your text cursor between the "i" and the "c". Hit BackSpace.
This generates an "object:text-changed:delete" event. The any_data.value()
field of that event should contain the character than has just been deleted.
Instead it contains the character to the left of the text cursor after the deletion
("u" in this example).

This makes it impossible for Orca, the screen reader/magnifier to correctly
report back to the user the character that they have just deleted.

ES: verfied in atkbridge4

ES->OBR: I can't reproduce the description (with which tool should I grab the
missing/existing info?) but I do believe "Delete characters won't be read".
Please have a look.

OBR: fixed commited to CWS atkbridge4

OBR->ES: you can check the character returned by enabling "Log events" in
at-poke and check object=>text-changed.

ES: Ok in m195

Comment 2 eric.savary 2006-12-01 11:26:29 UTC

Ok in m195

Comment 3 richburridge 2006-12-13 18:19:19 UTC

Just to verify, I downloaded OOo v2.1 (32bit Linux version) 
from the openoffice.org website and installed it.
With this version, I cannot reproduce the problem.