Search Results for "dom"

Happy DOM now supports Declarative Shadow DOM which can be used for server-side rendering of web components. This package makes it possible to use Happy DOM with Jest.

It's the first modern headless browsers designed specifically for scraping instead of just automated testing. Hero provides access to the W3C DOM specification without the need for Puppeteer's complicated evaluate callbacks and multi-context switching. We've recreated a fully compliant DOM directly in NodeJS allowing you bypass the headaches of previous scraper tools. The powerful Chrome engine sits under the hood, allowing for lightning fast rendering. Emulators make it easy to disguise your script as practically any browser.

...It supports flexible execution modes, allowing full-script runs when tasks are straightforward and step-by-step exploration when the agent needs to inspect or iterate carefully. To make automation more reliable for language models, it provides LLM-friendly DOM snapshots that structure the page in a way that is easier for an agent to interpret than raw HTML dumps.

...It comes with smart selector strategies that can, e.g. using the react$ command, fetch React components by its component name and filter it by its props or states. A similar command called $shadow provides the ability to fetch elements within the shadow DOM of a web component.

...What's more, BetterScroll also extends some features and optimizes for performance based on iscroll. BetterScroll is implemented with plain JavaScript, which means it's dependency free. BetterScroll provides a class whose first parameter is a plain DOM object when instantiated. Certainly, BetterScroll inside would try to use querySelector to get the DOM object. In BetterScroll 2.X, we split the 1.X-coupled feature into the plugin to achieve on-demand loading and reduce the volume of the package. Therefore, @better-scroll/core only provides the most core scrolling capabilities. If you want to implement the pull-up load, pull-down refresh function, you need to use the corresponding [plugin] (/en-US/plugins).