Open jkimmeyer opened 2 hours ago
@jkimmeyer, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
What happened?
When using Google Material Web Components, specifically the dialog component, all text within the dialog content slot is invisible to Selenium. The
get_element_text
method returns an empty string instead of the actual text content. However, filling the input or finding the label element (without text) works without any problems.I am uncertain whether this issue originates from Chromedriver or Selenium, as there appears to be some visibility logic within the Selenium repository. Could you please advise if I should file this issue under Chromedriver instead?
Reproduction Steps:
When running the dialog spec, tests are failing. The labels are visible but cannot be found using the
have_content
matchers.How can we reproduce the issue?
Code: https://github.com/jkimmeyer/selenium-example
Markup:
Test:
Relevant log output
Operating System
macOS Sequoia 15.0
Selenium version
Ruby 3.3.5
What are the browser(s) and version(s) where you see this issue?
Chrome 129
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 129
Are you using Selenium Grid?
No