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

BladeView isn't exposed correctly in UI Automation tree #3517

Closed
4 of 20 tasks
jamesmcroft opened this issue Oct 3, 2020 · 1 comment · Fixed by #3518
Closed
4 of 20 tasks

BladeView isn't exposed correctly in UI Automation tree #3517

jamesmcroft opened this issue Oct 3, 2020 · 1 comment · Fixed by #3518
Labels
Milestone

Comments

@jamesmcroft
Copy link
Member

Describe the bug

A clear and concise description of what the bug is.

When querying the BladeView and BladeItem controls using a tool for analyzing the UI Automation tree, the hierarchy of the UI is not rendered correctly making it difficult to automate UI tests.

  • Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:

NuGet Package(s):

  • Uwp.UI.Controls

Package Version(s):

  • 6.1.1

Windows 10 Build Number:

  • Fall Creators Update (16299)
  • April 2018 Update (17134)
  • October 2018 Update (17763)
  • May 2019 Update (18362)
  • May 2020 Update (19041)
  • Insider Build (build number: )

App min and target version:

  • Fall Creators Update (16299)
  • April 2018 Update (17134)
  • October 2018 Update (17763)
  • May 2019 Update (18362)
  • May 2020 Update (19041)
  • Insider Build (xxxxx)

Device form factor:

  • Desktop
  • Xbox
  • Surface Hub
  • IoT

Visual Studio

  • 2017 (version: )
  • 2019 (version: 16.7.4)
  • 2019 Preview (version: )
@jamesmcroft jamesmcroft added the bug 🐛 An unexpected issue that highlights incorrect behavior label Oct 3, 2020
@ghost ghost added the needs triage 🔍 label Oct 3, 2020
@ghost
Copy link

ghost commented Oct 3, 2020

Hello jamesmcroft, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

@ghost ghost added the In-PR 🚀 label Oct 3, 2020
@michael-hawker michael-hawker added this to the 7.0 milestone Oct 6, 2020
@ghost ghost removed the needs triage 🔍 label Oct 6, 2020
@ghost ghost added the in progress 🚧 label Dec 9, 2020
@ghost ghost added Completed 🔥 and removed In-PR 🚀 labels Dec 15, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Feb 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants