You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling axe.commons.dom.isVisible on the .target element results in true, even though visually the element is hidden. However, if we swap the width/height values, the element is then considered hidden. It seems our isVisible function only looks at height as a way to hide the element but does not consider width.
Validated with the latest axe-core develop branch code base,
seeing scrollable-region-focusible failing when width of scroll regions is zero (0), using color-constrast
Consider the following dom:
Calling
axe.commons.dom.isVisible
on the.target
element results intrue
, even though visually the element is hidden. However, if we swap the width/height values, the element is then considered hidden. It seems our isVisible function only looks at height as a way to hide the element but does not consider width.This is the cause of #2674
The text was updated successfully, but these errors were encountered: