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
Working on some shadow DOM stuff, I noticed that in order to determine whether there are multiple children in the shadow root, we're checking parentElement. For children of the shadow root this is null, which results in an ancestry that just uses the node name. You can reproduce it in the following:
This will give ['html > body > custom-elm', 'button'] as the ancestry for. BOTH buttons. This doesn't seem to happen with the regular selector axe-core has, which is probably why this has gone unnoticed for so long.
The text was updated successfully, but these errors were encountered:
Working on some shadow DOM stuff, I noticed that in order to determine whether there are multiple children in the shadow root, we're checking parentElement. For children of the shadow root this is null, which results in an ancestry that just uses the node name. You can reproduce it in the following:
This will give
['html > body > custom-elm', 'button']
as the ancestry for. BOTH buttons. This doesn't seem to happen with the regularselector
axe-core has, which is probably why this has gone unnoticed for so long.The text was updated successfully, but these errors were encountered: