Enter a search term above to see results...
On This Page
Introduction
Query is a library built to make it easy to interact with a page’s DOM and shadow DOM in a chainable way. Query was custom built to make it easy to handle web components and access their inner DOM trees using a single jQuery like syntax.
Query includes many of the helpers which make it easy to interact with web components, emit and consume events, traverse the DOM tree, retreive common values and much more.
API Reference — For a more thorough explanation of functionality visit the API reference guide.
Why Create a Library
Web components are built around encapsulating portions of the DOM in the Shadow DOM, which prevent easy access or reference from other scopes.
Many common usage patterns for developers require traversing the DOM, but with native APIs these will stop at shadow DOM root or slotted content boundaries. Doing this deeply or recursively is also basically impossible without writing your own helpers.
Query helps give you all the utilities like closest
, find
, siblings
but while giving you options for traversing these boundaries.
Accessing DOM
Query provides two exports $
and $$
.
$
is used for querying the normal browser DOM and $$
is for querying the shadow DOM (the DOM present in web components).
$ - Standard DOM
$
is designed to allow for extremely performant chaining for normal DOM nodes.
$ Performance - Query uses native
querySelector
and modern DOM APIs which means the performance implications are low when using$
.
$$ - Shadow DOM
$$
allows for accessing DOM nodes regardless of where they are in the page.
Web components have portions of their DOM encapsulated in what is known as the Shadow DOM which can only be accessed with el.shadowRoot.querySelector
, and portions of shadow DOM have content slots which can only access content via el.slottedNodes
.
The $$
helps traverse these boundaries to access children or parent nodes in a way similar to $
.
$$ Performance -
$$
must pierce shadow DOM boundaries recursively which can reduce perfomance over$
. For most use-cases this difference is negligible (less than 1ms), but for complex DOM trees the cost can be more significant. For this reason it is recommended to use$$
only when necessary to avoid performance roadblocks in your app.
DOM Example
The following example shows the difference in selectors between $
and $$
from inside a web component.
Chaining
Query is built on the concept of chaining, which was originally pioneered by jQuery, where method can be called in a pipeline processing the results of previous method calls.
To see more examples of chaining browse the Query API docs.
Additional Options
You can specify additional options when initializing the Query
class.
Root
In some advanced cases you might want to limit Query to a particular root element.
Pierce Shadow
$$
is the same as passing pierceShadow: true
as an option to $
but is provided for convenience as a separate export.
Usage
Browser
In a browser environment you can use exportGlobals
to export $ and $$ for use in your page. For more fine grained control see the browser helpers section below
Components
$
and $$
are integrated into all lifecycle callbacks and events in Semantic UI components.
Browser Helpers
A few additional helpers are provided specifically for using Query in browser environments.
For more information see the API reference.
Restoring Globals
If you need to restore the previous values before calling export globals.
Custom Aliases
You can also choose to use Query as a custom alias