The W3C's Web Component Standard was published in 2014 and has been used more and more for several years. The reason for this is the uniformity of browser support (IE11 + Edge Chromium).
It makes strategic and economic sense to develop framework-agnostic components, and these are Web Components. The shadow root ensures robust behavior of the components here.
In recent years, browser extensions, testing tools, etc. have also added support for Shadow-Roots as more and more websites use Web Components.
For example: Nightwatch.js, Microsoft Playwight, Selenium
We ask Nuonce Dragon to optimize the detection of the DOM and accessibility trees so that all Sub-DOMs in Shadow-Roots are also detected. The algorithm is very simple, because when a Shadow-Root node is detected, it can simply continue scanning one more level down.
Thanks a lot.
Note
Do you also rely on Nuance Dragon and need this feature, then like this issue too.
👇
The W3C's Web Component Standard was published in 2014 and has been used more and more for several years. The reason for this is the uniformity of browser support (IE11 + Edge Chromium).
It makes strategic and economic sense to develop framework-agnostic components, and these are Web Components. The shadow root ensures robust behavior of the components here.
In recent years, browser extensions, testing tools, etc. have also added support for Shadow-Roots as more and more websites use Web Components.
For example: Nightwatch.js, Microsoft Playwight, Selenium
We ask Nuonce Dragon to optimize the detection of the DOM and accessibility trees so that all Sub-DOMs in Shadow-Roots are also detected. The algorithm is very simple, because when a Shadow-Root node is detected, it can simply continue scanning one more level down.
Thanks a lot.