Issue 22053 - gnome screen reader(gnopernicus) not reading selected text
Summary: gnome screen reader(gnopernicus) not reading selected text
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: current
Hardware: PC Linux, all
: P2 Trivial with 2 votes (vote)
Target Milestone: OOo 2.0.2
Assignee: eric.savary
QA Contact: issues@ui
Keywords: accessibility
: 25401 32928 (view as issue list)
Depends on:
Reported: 2003-11-03 11:46 UTC by Unknown
Modified: 2006-02-09 09:30 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-11-03 11:46:59 UTC
using a gnome-2.4 build from 24/10/03
using StarOffice 7 build from 31/10/03


-launch staroffice 7
-launch gnopernicus with speech enabled
-open a new text file
-type a sample text document
-highlight a portion of text from the document
-gnopernicus does not read out the selected text


-the selected text in StarOffice should be reported by gnopernicus
Comment 1 mci 2003-11-20 15:00:04 UTC
reassigned to es

@es: I think this is something for you...
Comment 2 eric.savary 2003-11-26 11:05:03 UTC
ES->RU: please evaluate.
Comment 3 ru 2003-12-18 09:29:23 UTC
RU -> OBR: I compared the current SO behaviour with the behaviour of gedit. In
gedit every marked character is reported. When one removes the text marking
again screen reader reports "No selection anymore" Neither of them is reported
in SO.

RU: This bug is a candidate for Cinnabar.

Comment 4 ru 2003-12-18 09:30:07 UTC
Comment 5 nospam4obr 2004-02-12 14:22:10 UTC
*** Issue 25401 has been marked as a duplicate of this issue. ***
Comment 6 nospam4obr 2004-02-13 13:08:03 UTC does not yet implement TEXT_SELECTION_CHANGED events. I am not
sure why gnopernicus seems to ignore caret events while shift key is pressed though.

Changing all (four) text implementations in the Office is unlikely to happen in
the 1.1.x time frame, so I re-target this to 2.0.
Comment 7 andreas.martens 2004-06-22 10:28:05 UTC
Because of a shortage of resources we have to retarget this issue to OOo later. 
Comment 8 nospam4obr 2004-08-23 08:45:54 UTC
*** Issue 32928 has been marked as a duplicate of this issue. ***
Comment 9 dormenisan 2004-08-27 13:59:49 UTC
Gnopernicus ignores the caret events while shift key is pressed because it
checks if there is a selection for this text object. 
So, if AccessibleText_getNSelection!=0, from gnopernicus point of view there is
a selection which should be reported and the 'caret:moved' event is ignored.
Comment 10 mdxonefour 2004-08-30 12:17:38 UTC
Due to the importance of this issue, re-targeted to OOo 2.0
Comment 11 christof.pintaske 2004-10-29 15:38:27 UTC
retarget to later due to missing ressources
Comment 12 christof.pintaske 2004-10-29 15:43:54 UTC
Comment 13 mdxonefour 2005-06-14 11:04:32 UTC
re-targeted to "OOo 2.0.2" and changed priority to "P2" because of severe
missing functionality
Comment 14 mdxonefour 2005-09-29 11:05:05 UTC
re-targeted to OOo 3.0
Comment 15 mdxonefour 2005-09-29 16:34:27 UTC
re-targeted to OOo 2.0.2, re-targeting to OOo 3.0 was done by error
Comment 16 nospam4obr 2006-01-09 11:07:05 UTC
Meanwhile a workaround for the missing TEXT_SELECTION_CHANGED events has been
implemented in the Java AccessBridge for GNOME. However, these events are now
generated by all OOo text components, so that this will (hopefully) not break
when switching to a UNO <-> ATK bridge.
Comment 17 nospam4obr 2006-01-16 09:51:52 UTC
obr -> es: please verify that recent changes for TEXT_SELECTION_CHANGED support
did not break gnopernicus reading selections. 

However, even with FLOWS_FROM/FLOWS_TO relations now implemented, I can't see
any improvements in multi-paragraph selections :(.
Comment 18 nospam4obr 2006-01-16 09:53:59 UTC
Comment 19 nospam4obr 2006-01-16 09:58:40 UTC
Restoring FIXED state.
Comment 20 eric.savary 2006-01-17 16:33:08 UTC
Verified in CWS swqbf49
Comment 21 eric.savary 2006-02-09 09:30:17 UTC
Ok in src680m156