Skip to content

New UIA support and Braille not working #10191

Closed

Description

@vincent-lg

The support for UIA in console leads to a lot of problems in Braille.

Steps to reproduce

  1. Activate the UIA support for the Windows console in NVDA preferences.
  2. Start a console with a Braille display.
  3. And browse in review. No need to go far to see the problems.

Excerpt

Here is an excerpt for my own Windows console. When I open it, the review cursor is able to read the following:

Microsoft Windows [Version 10.0.17763.678]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\Admin>

My Braille display, when scrolling with the review cursor (with pavnum7 and pavnum9 on a computer keyboard) reads the following:

78]
 Corporation. All rights reserved.

CC:\Users\Admin>

(The CC on the last line doesn't appear the first time, it only appears when browsing back to it, which shows some problems.)

So I'd say there is a problem. And when using the Braille keys to scroll, things get even more weird. I don't think I need to supply a full transcript: comparing outputs in the previous transcripts should show lots of problems.

So I would highly advise: please don't merge it or do some proper testing in Braille. Although the feature can be turned off, it's definitely on by default.

I'll be happy to do further testing if need be.

Information:

  • Windows 10 (see signature above if needed)
  • NVDA snapshot: alpha-18590,50619158
  • Braille display: HandyTech ActiveBraille

Thanks!

Activity

  1. Adriani90 commented on Sep 11, 2019

    @Adriani90
    Collaborator
  2. LeonarddeR commented on Sep 11, 2019

    @LeonarddeR
    Collaborator
  3. self-assigned this
    on Nov 6, 2019
  4. LeonarddeR commented on Nov 6, 2019

    @LeonarddeR
    Collaborator

    Turns out that the collapse method is broken when invoked for a textInfo that's positioned at the start of a line.

  5. removed their assignment
    on Nov 6, 2019
  6. LeonarddeR commented on Nov 6, 2019

    @LeonarddeR
    Collaborator

    Quick investigation revealed that it looks pretty complicated to fix this. Whatever I do with moving endpoints of the range, when positioned at the first character in the text, it simply refuses to collapse.

  7. zstanecic commented on Nov 6, 2019

    @zstanecic
    Contributor
  8. lukaszgo1 commented on Nov 9, 2019

    @lukaszgo1
    Contributor

    @zstanecic If you are still experiencing these problems please open separate issue for them.

  9. added this to the 2019.3 milestone on Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions