After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 704620 - Accessible caret-moved event is sometimes for the wrong text object
Accessible caret-moved event is sometimes for the wrong text object
Status: RESOLVED DUPLICATE of bug 724965
Product: evince
Classification: Core
Component: general
unspecified
Other Linux
: Low normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks: 677348
 
 
Reported: 2013-07-20 21:16 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2014-06-10 17:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
PDF test case (15.39 KB, application/pdf)
2013-07-20 21:17 UTC, Joanmarie Diggs (IRC: joanie) 		Details
event listener (326 bytes, text/plain)
2013-07-20 21:17 UTC, Joanmarie Diggs (IRC: joanie) 		Details

Description Joanmarie Diggs (IRC: joanie) 2013-07-20 21:16:21 UTC 
Steps to reproduce:
1. Open the to-be-attached PDF
2. Enable caret navigation (see bug 702079)
3. Run the attached listener in a terminal.
4. Click within the text on each page.

Expected results: The full text of the current page would be printed.

Actual results: The full text of the first page is printed.

Note: If you arrow instead of click, the contents are correct for both pages.
Comment 1 Joanmarie Diggs (IRC: joanie) 2013-07-20 21:17:01 UTC 
Created attachment 249719 [details]
PDF test case
Comment 2 Joanmarie Diggs (IRC: joanie) 2013-07-20 21:17:44 UTC 
Created attachment 249720 [details]
event listener
Comment 3 Joanmarie Diggs (IRC: joanie) 2013-07-26 15:25:13 UTC 
This, by the way, is a should-fix-but-can-wait bug I discovered whilst testing another issue.

The reason it can wait is that Orca users will not be mouse-clicking; they will be keyboard-navigating. And we'll need to first fix/rework ev-view-accessible anyway as part of the tagged pdf support, so this issue might get fixed by side effect.

Lowering the priority accordingly.
Comment 4 Joanmarie Diggs (IRC: joanie) 2014-06-10 17:02:29 UTC 
The issue in the opening report was fixed as a consequence of fixing other bugs. If I had to bet, my money would be on bug 724965 as that is where each page became an accessible object the content of which could be obtained independent of caret navigation. Thus marking this one as a dup of that one.

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