Skip to content
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

Microsoft Edge UIA Framework ID changed #5955

Closed
michaelDCurran opened this issue May 16, 2016 · 4 comments
Closed

Microsoft Edge UIA Framework ID changed #5955

michaelDCurran opened this issue May 16, 2016 · 4 comments
Assignees
Milestone

Comments

@michaelDCurran
Copy link
Contributor

@michaelDCurran michaelDCurran commented May 16, 2016

As of Windows 10 build 14328, the UIA framework ID for Edge is now MicrosoftEdge, rather than InternetExplorer.
NVDA must be changed to detect this so as to provide browse mode for later builds of Edge.
Issue #5901 also depends on this.

@nvaccessAuto
Copy link

@nvaccessAuto nvaccessAuto commented May 16, 2016

Incubated in d5f3732.

@josephsl
Copy link
Collaborator

@josephsl josephsl commented Jun 9, 2016

Hi,

I'm not sure if the below issue has anything to do with this...

A variant of #5901: In build 14361, if you restart NVDA, NVDA will fail to notice UIA item selection event.

STR:

  1. Tell NVDA to start after you log onto your computer.
  2. Restart your computer.
  3. Open Start, then search for something.
  4. Restart NvDA and repeat step 3.

Expected: NVDA will notice UIA item selection event.
Actual: No search results announcement.

Setup:

  • NVDA version: next.13351
  • OS: Windows 10 Build 14361
  • Reproducible: Yes.

Other than this, UIA is functioning as expected - recognizes various UIA controls, for instance. Thanks.

@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented Jun 9, 2016

@josephsl
Copy link
Collaborator

@josephsl josephsl commented Jun 15, 2016

Hi,
Last issue fixed as of build 14366. Thanks.

@nvaccessAuto nvaccessAuto removed the incubating label Jul 8, 2016
@jcsteh jcsteh added this to the 2016.3 milestone Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.