Search Results for "dom"

Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. It includes many web standards from WHATWG DOM and HTML. The goal of Happy DOM is to emulate enough of a web browser to be useful for testing, scraping web sites, and server-side rendering. Happy DOM focuses heavily on performance and can be used as an alternative to JSDOM. Happy DOM now supports Declarative Shadow DOM which can be used for server-side rendering of web components. This package makes...

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...

... such as React, Angular, Polymeror Vue.js as well as native mobile applications for Android and iOS. 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.

... for change. Ayakashi's way of finding things in the page and using them is done with props and domQL. Directly inspired by the relational database world (and SQL), domQL makes DOM access easy and readable no matter how obscure the page's structure is. Props are the way to package domQL expressions as re-usable structures which can then be passed around to actions or to be used as models for data extraction.

... 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).