[🐛 Bug]: popover attribute is not handled

[toy]

What happened?

I was testing using capybara interaction with buttons that are in an element with popover attribute which is inside an element with overflow hidden. Capybara doesn't handle visibility of elements inside an element with popover attribute, but after fixing that I am getting Selenium::WebDriver::Error::ElementNotInteractableError.

Related issue: teamcapybara/capybara#2755

How can we reproduce the issue?

HTML to show the problem:

<div style="position: relative; overflow: hidden;">
  <button popovertarget="show">Show popover</button>
  <button style="position: absolute; top: 30px;">Can not be clicked</button>
  <button popover id="show" style="position: absolute; top: 60px;">Should be clickable</button>
</div>

After clicking the «Show popover»:

It should not be possible to click the «Can not be clicked» button, but it should be possible to click the «Should be clickable» button.

Relevant log output

Selenium::WebDriver::Error::ElementNotInteractableError:
       element not interactable
         (Session info: chrome-headless-shell=121.0.6167.85)
     # 0   chromedriver                        0x0000000104d1e814 chromedriver + 4040724
     # 1   chromedriver                        0x0000000104d16a18 chromedriver + 4008472
     # 2   chromedriver                        0x00000001049896a8 chromedriver + 284328
     # 3   chromedriver                        0x00000001049ce330 chromedriver + 566064
     # 4   chromedriver                        0x00000001049c34b8 chromedriver + 521400
     # 5   chromedriver                        0x00000001049c2ee8 chromedriver + 519912
     # 6   chromedriver                        0x0000000104a07048 chromedriver + 798792
     # 7   chromedriver                        0x00000001049c174c chromedriver + 513868
     # 8   chromedriver                        0x00000001049c2044 chromedriver + 516164
     # 9   chromedriver                        0x0000000104ce3a3c chromedriver + 3799612
     # 10  chromedriver                        0x0000000104ce7f1c chromedriver + 3817244
     # 11  chromedriver                        0x0000000104ccc298 chromedriver + 3703448
     # 12  chromedriver                        0x0000000104ce8a64 chromedriver + 3820132
     # 13  chromedriver                        0x0000000104cbf054 chromedriver + 3649620
     # 14  chromedriver                        0x0000000104d05e74 chromedriver + 3939956
     # 15  chromedriver                        0x0000000104d05fec chromedriver + 3940332
     # 16  chromedriver                        0x0000000104d16698 chromedriver + 4007576
     # 17  libsystem_pthread.dylib             0x0000000182092034 _pthread_start + 136
     # 18  libsystem_pthread.dylib             0x000000018208ce3c thread_start + 8

Operating System

macOS Sonoma

Selenium version

selenium-webdriver 4.18.1

What are the browser(s) and version(s) where you see this issue?

Chrome 121.0.6167.85

What are the browser driver(s) and version(s) where you see this issue?

ChromeDriver 121.0.6167.184 (057a8ae7deb3374d0f1b04b36304d236f0136188-refs/branch-heads/6167@{#1818})

Are you using Selenium Grid?

No response

[github-actions]

@toy, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

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!

[titusfortner]

Visibility is typically managed by Selenium, though Capybara has an optimized version that it maintains independently.
interactibiity, though, is managed by chromedriver, not by Selenium.

You might also try --headless=new, since it is possible it works with Chrome, but not chrome-headless-shell

[github-actions]

Hi, @toy.
This issue has been determined to require fixes in ChromeDriver.

You can see if the feature is passing in the Web Platform Tests.

If it is something new, please create an issue with the ChromeDriver team.
Feel free to comment the issues that you raise back in this issue. Thank you.

[toy]

@titusfortner Thank you for looking into the issue. I have checked that it is there also for Chrome and not only for headless browser

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.