Support text selection in display model

[nvaccessAuto]

Reported by jeronimo on 2010-07-19 17:29
I suggest to add support for selecting text in areas Windows Live applications in Eclipse in Textpad, in Eudora, in Australian e-tax and bars in Microsoft Excel formulas.
Blocking #1917, #2691, #2946

[nvaccessAuto]

Comment 1 by jteh on 2010-07-19 17:33
Eclipse uses IAccessible2, so text selection is already supported there.
Changes:
Changed title from "Added support for selecting text in areas Windows Live applications in Eclipse in Textpad, in Eudora, in Australian e-tax and bars in Microsoft Excel formulas." to "Support text selection in display model"
Milestone changed from 2010.2 to None

[nvaccessAuto]

Comment by jteh on 2012-09-29 06:46
(In #2691) This is because the editable text control used by Eudora is non-standard and doesn't support standard accessibility APIs, so we have to fall back to display model.

[nvaccessAuto]

Comment 4 by Michael Curran <mick@... on 2014-02-12 00:20
In [47f8213]:

Merge branch 't770' into next. Incubates #770

Changes:
Added labels: incubating

[nvaccessAuto]

Comment 5 by Michael Curran <mick@... on 2014-02-27 04:50
In [f76996a]:

Merge branch 't770'. Fixes #770

Changes:
Removed labels: incubating
State: closed

[nvaccessAuto]

Comment 6 by mdcurran on 2014-02-27 04:57
Changes:
Milestone changed from None to 2014.2

[nvaccessAuto]

Comment 7 by fatma.mehanna on 2014-03-03 10:24
this ticket should announce what's being selected in excel. right?
when i want to modify a cell by pressing f2, and selecting some chars/numbers, NVDA doesn't announce what i'm selecting.
i use office 2010

[nvaccessAuto]

Comment 8 by jteh on 2014-03-03 14:56
It doesn't work in Excel. We're not sure why, but NVDA can't seem to detect any change to the colour of the text when it's selected. We can only guess that Excel uses some non-standard/strange way to highlight the selected text that we don't know how to detect.

[Adriani90]

@michaelDCurran, @jcsteh, it seems solved as it is in
f76996a]:
Merge branch 't770'. Fixes #770

Apparently this blocked #2946. Is this still the case? Or is #2946 solved?

[jcsteh]

Yes, this issue (#770) is fixed. While this issue was a prerequisite for #2946, it unfortunately didn't fix #2946 all by itself as we hoped it would; see #2946 (comment) for explanation.