Bug 50926

Summary:	libreoffice writer provides incorrect information to atk if "record" is enabled in the changes menu
Product:	LibreOffice	Reporter:	prayner
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	jdiggs
Priority:	medium
Version:	3.5.3 release
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description prayner 2012-06-09 22:52:19 UTC

Noticed using orca
to duplicate:
1) start orca with --debug
2) start libreoffice writer
3) open a "new" empty file from the file menu
4) enter some text
5) go to the "changes" menu and turn on "record"
6) return to the empty file and use the home key to return to the start of the line
7) insert some more text
8) look at the debug output from orca, particularly the lines comencing "VISIBLE:", these will not show any change as the new text is inserted

Comment 1 Jason White 2012-11-22 23:47:41 UTC

Confirmed in 3.6.3~rc2-1+b1 from debian with Orca 3.4.2-2.

Comment 2 chrys87@web.de 2013-01-17 01:59:25 UTC

i can also confirm on fedora 18.
may be the same reason like this? https://bugs.freedesktop.org/show_bug.cgi?id=56031
cheers

Comment 3 Joanmarie Diggs 2013-02-15 14:26:19 UTC

I strongly suspect this has nothing to do with "record" being enabled and is a duplicate of bug 56031.

Peter, if you perform the steps in your opening report but skip step 5, do you still see this bug?

Comment 4 prayner 2013-02-16 01:46:53 UTC

reply to comment 3: I cannot test this on 3.5.3 any more but you are right with 3.6.5 which is hence unusable

Comment 5 Joanmarie Diggs 2013-02-16 03:03:05 UTC

(In reply to comment #4)
> reply to comment 3: I cannot test this on 3.5.3 any more but you are right
> with 3.6.5 which is hence unusable

If there are no objections then, I'm going to close this as a duplicate of bug 56031. If new evidence surfaces to prove there is some connection between "record" and AtkText breakage independent of bug 56031, this can be reopened.

*** This bug has been marked as a duplicate of bug 56031 ***