Could some one from MTV please look into the issue, as it is related to Selenium WebDriver.
Thanks in Advance.

[mac bug triage] setting component

dylan.barrell@,

The attached screenshot shows that you are pointing to two different elements in the Chrome launched by Chromedriver and in the regular Chrome.
Anyway I checked all the slot elements but I do not see any difference.

Chrome browser 59.0.3071.86 that you are using is an older version. Please upgrade to the current stable v61.0.3163.91. You may navigate to chrome://help to automatically update the browser version.
Also, do you see any issue/error during Chromedriver testing due to the difference in display property?

The issue that I have is that the accessibility testing tool we develop creates a bad flattened tree when run inside of Chromedriver - leading to false accessibility outcomes for tests. This is the same engine that is embedded inside the Chrome Audits tool and automatable as part of the Google Lighthouse project. We have temporarily worked around this by ignoring the display property on all slots - this in itself can lead to problems.

I may have highlighted different elements, but all slot elements are supposed to have display:contents unless changed by the CSS - which is not happening on that page.

On June 9th, Chromedriver 59 was the newest version. If you think the problem is no longer showing up in 61, then close the bug. I will re-open it if it re-surfaces.

Thank you for providing more feedback. Adding requester "gmanikpure@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I have been unable to repro this bug. With both Chrome 59 and 61, and both with and without ChromeDriver, I got the same result, that all the slot elements have display: block. I haven't been able to see any cases where they receive display: contents.

Gauri: Could you please also give it a try? Thanks.

Yes John, I am also unable to reproduce the bug on current Chrome stable v61.0.3163.91 with & without Chromedriver. 

I think we can close this issue.

dylan.barrell@, if you see the issue again, please provide reproducible test.

Gauri: Thanks for the information.

dylan.barrell@deque.com: I'm closing this bug as we were unable to repro it. If you are still experiencing this issue with latest Chrome, please do let us know and provide any additional information you may have, and we'll look further. Thanks.

Wait - If all the slot elements have display:block - THAT IS THE PROBLEM!!

slot elements are supposed to have display:contents by default.

I don't know enough about CSS for the default slot element style. Since this bug report was about Chrome behave differently when called from ChromeDriver, I was merely stating that I wasn't able to repro any differences with or without ChromeDriver.

Could you please open a new bug about the wrong style applied to slot elements? Please label it as a style problem, so that it can be routed correctly? Thanks.