Element available for interacting even if it's hidden by {overflow: hidden}

[GeyseR]

Hi!

I'm not sure is current behavior expected or not, so I decided to file a ticket for selenium dev team. For some reason locating and interacting with an invisible element on the page is working for me. The element is presented in DOM but it's hidden by parent's {overflow: hidden} css.

Meta -

OS:
Ubuntu
Selenium Version:
3.8.1
Browser:
Chrome
Browser Version:
63.0.3239.84

Expected Behavior -

id_displayed returns False and element is not clickable

Actual Behavior -

id_displayed returns True and element is not clickable

Steps to reproduce -

html/styles: https://jsfiddle.net/ck6utghr/

browser = webdriver.Remote(url, capabilities)
browser.get('test.html')
wait = WebDriverWait(browser, timeout=20)
wait.until(
    EC.visibility_of_element_located((By.CSS_SELECTOR, '.target-link')),
)
link = browser.find_element_by_css_selector('.target-link')
link.click()

[p0deje]

I'm not an expert in CSS so I don't really know how overflow should be handled in all the cases. I see that there is quite a lot of logic around handling overflow state when checking for element visibility:

selenium/javascript/atoms/dom.js

Lines 520 to 528 in b3cda32

	// Elements that are hidden by overflow are not shown.
	function hiddenByOverflow(e) {
	return bot.dom.getOverflowState(e) == bot.dom.OverflowState.HIDDEN &&
	goog.array.every(e.childNodes, function(n) {
	return !bot.dom.isElement(n) || hiddenByOverflow(n) ||
	!positiveSize(n);
	});
	}
	return !hiddenByOverflow(elem);

Still, this particular case looks like a bug in atoms that we haven't encountered yet. I don't think I can fix it, so it would be great if somebody with a better understanding could have a look (cc @barancev @AutomatedTester).

[github-actions]

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.

[github-actions]

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