I see the issue clearly from your screenshot.
Shadow DOM access uses Selenium 4's built-in WebElement.getShadowRoot() rather than a JS-executor workaround. Each scenario gets a fresh browser session (@Before / @After in Hooks.java), so scenarios ...
一些您可能无法访问的结果已被隐去。
显示无法访问的结果