New issue
Advanced search Search tips

Issue 873138 link

Starred by 2 users
Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

UI Automation Element Changes

Reported by tony.val...@gmail.com, Aug 10 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
As part of the upcoming Material Design changes, Chrome 68 has reorganized some UI elements but has forgotten to include the UI element names. This causes problems for accessibility applications and UI automation applications which rely on this information.

What is the expected behavior?
The main navigation elements should have names associated with them.

What went wrong?
Element paths have changed and the lack of names make finding the correct element significantly harder.

Did this work before? N/A 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: 10.0
Flash Version: 

I've attached a screen shot from Microsoft's Visual UI Automation Verify showing places where empty element names cause problems as well as proposed element names.
Chrome UI Elements.png
116 KB View Download

Comment 1 by swarnasree.mukkala@chromium.org, Aug 12

Labels: Needs-Triage-M68

Comment 2 by kozy@chromium.org, Aug 13

Components: -Platform>DevTools UI
I believe that it is note related to Chrome DevTools.

Comment 3 by viswa.karala@chromium.org, Aug 13

Labels: Triaged-ET TE-NeedsTriageHelp
Thanks for filing the issue!

As per comment# 0, the issue seems to be related to Microsoft's Visual UI Automation which is out of scope for TE, hence adding "TE-NeedsTriageHelp" label and requesting someone from the respective team have a look at this issue and help in further triaging it.

Thanks!

Comment 4 by jbanavatu@chromium.org, Nov 16

Labels: Hotlist-DesktopUIChecked Hotlist-DesktopUIToolingRequired
**UI mass Triage**
►

Sign in to add a comment