/nvda

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review cursor doesn't follow virtual caret in PowerPoint Slide Show #4370

Closed
nvaccessAuto opened this Issue Aug 8, 2014 · 3 comments

Comments

Assignees

@michaelDCurran michaelDCurran

Labels
Projects
None yet
Milestone
  2014.4
2 participants
@nvaccessAuto @michaelDCurran
@nvaccessAuto

nvaccessAuto commented Aug 8, 2014

Reported by jteh on 2014-08-08 05:53
Str:

  1. Create a new PowerPoint presentation.
  2. In the center title, type: abc
  3. Press f5.
  4. Press right arrow to move the cursor to: b
  5. Press numpad2.
  • Expected: b
  • Actual: a
@nvaccessAuto

This comment has been minimized.

Sign in to view

nvaccessAuto commented Aug 12, 2014

Comment 1 by Michael Curran <mick@... on 2014-08-12 05:00
In [57dce93]:

Merge branch 't4370' into next. Incubates #4370

Changes:
Added labels: incubating
@nvaccessAuto

This comment has been minimized.

Sign in to view

nvaccessAuto commented Sep 4, 2014

Comment 2 by Michael Curran <mick@... on 2014-09-04 04:25
In [088aecb]:

Merge branch 't4370'. Fixes #4370

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto

This comment has been minimized.

Sign in to view

nvaccessAuto commented Sep 4, 2014

Comment 3 by mdcurran on 2014-09-04 04:27
Changes:
Milestone changed from next to 2014.4

@nvaccessAuto nvaccessAuto added bug Microsoft Office support labels Nov 10, 2015

@nvaccessAuto nvaccessAuto assigned michaelDCurran Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2014.4 milestone Nov 10, 2015

@nvaccessAuto nvaccessAuto closed this Nov 10, 2015

@nvaccessAuto nvaccessAuto referenced this issue Nov 10, 2015

Closed

English What's New 2015.3: minor linguistic corrections #5414

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment