ReactiveElement

Base element class which manages element properties and attributes. When properties change, the update method is asynchronously called. This method should be supplied by subclassers to render updates as desired.

Import

attributeChangedCallback(name, _old, value): void

Permalink to attributeChangedCallback View source

Synchronizes property values when attributes change.

Parameters
name
string
_old
null | string
value
null | string
Details

Specifically, when an attribute is set, the corresponding property is set. You should rarely need to implement this callback. If this method is overridden, super.attributeChangedCallback(name, _old, value) must be called. See using the lifecycle callbacks on MDN for more information about the attributeChangedCallback.

static observedAttributes: Array<string>

Permalink to observedAttributes View source

Returns a list of attributes corresponding to the registered properties.

addController(controller): void

Permalink to addController View source

Registers a ReactiveController to participate in the element's reactive update cycle. The element automatically calls into any registered controllers during its lifecycle callbacks.

Parameters
controller
ReactiveController
Details

If the element is connected when addController() is called, the controller's hostConnected() callback will be immediately called.

removeController(controller): void

Permalink to removeController View source

Removes a ReactiveController from the element.

Parameters
controller
ReactiveController

static disableWarning?: (warningKind: WarningKind) => void

Permalink to disableWarning View source

Disable the given warning category for this class.

Details

This method only exists in development builds, so it should be accessed with a guard like:

Read or set all the enabled warning categories for this class.

Details

This property is only used in development builds.

static enableWarning?: (warningKind: WarningKind) => void

Permalink to enableWarning View source

Enable the given warning category for this class.

Details

This method only exists in development builds, so it should be accessed with a guard like:

On first connection, creates the element's renderRoot, sets up element styling, and enables updating.

Allows for super.disconnectedCallback() in extensions while reserving the possibility of making non-breaking feature additions when disconnecting at some point in the future.

static addInitializer(initializer): void

Permalink to addInitializer View source

Adds an initializer function to the class that is called during instance construction.

Parameters
initializer
Initializer
Details

This is useful for code that runs against a ReactiveElement subclass, such as a decorator, that needs to do work for each instance, such as setting up a ReactiveController.

Decorating a field will then cause each instance to run an initializer that adds a controller:

Initializers are stored per-constructor. Adding an initializer to a subclass does not add it to a superclass. Since initializers are run in constructors, initializers will run in order of the class hierarchy, starting with superclasses and progressing to the instance's class.

static finalize(): boolean

Permalink to finalize View source

Creates property accessors for registered properties, sets up element styling, and ensures any superclasses are also finalized. Returns true if the element was finalized.

static finalized: boolean

Permalink to finalized View source

Marks class as having finished creating properties.

static createProperty(name, options?): void

Permalink to createProperty View source

Creates a property accessor on the element prototype if one does not exist and stores a PropertyDeclaration for the property with the given options. The property setter calls the property's hasChanged property option or uses a strict identity check to determine whether or not to request an update.

Parameters
name
PropertyKey
options?
PropertyDeclaration<unknown, unknown>
Details

This method may be overridden to customize properties; however, when doing so, it's important to call super.createProperty to ensure the property is setup correctly. This method calls getPropertyDescriptor internally to get a descriptor to install. To customize what properties do when they are get or set, override getPropertyDescriptor. To customize the options for a property, implement createProperty like this:

static elementProperties: PropertyDeclarationMap

Permalink to elementProperties View source

Memoized list of all element properties, including any superclass properties. Created lazily on user subclasses when finalizing the class.

static getPropertyDescriptor(name, key, options): undefined | PropertyDescriptor

Permalink to getPropertyDescriptor View source

Returns a property descriptor to be defined on the given named property. If no descriptor is returned, the property will not become an accessor. For example,

Parameters
name
PropertyKey
key
string | symbol
options
PropertyDeclaration<unknown, unknown>
Details

static getPropertyOptions(name): PropertyDeclaration<unknown, unknown>

Permalink to getPropertyOptions View source

Returns the property options associated with the given property. These options are defined with a PropertyDeclaration via the properties object or the @property decorator and are registered in createProperty(...).

Parameters
name
PropertyKey
Details

Note, this method should be considered "final" and not overridden. To customize the options for a given property, override createProperty.

User-supplied object that maps property names to PropertyDeclaration objects containing options for configuring reactive properties. When a reactive property is set the element will update and render.

Details

By default properties are public fields, and as such, they should be considered as primarily settable by element users, either via attribute or the property itself. Generally, properties that are changed by the element should be private or protected fields and should use the state: true option. Properties marked as state do not reflect from the corresponding attribute However, sometimes element code does need to set a public property. This should typically only be done in response to user interaction, and an event should be fired informing the user; for example, a checkbox sets its checked property when clicked and fires a changed event. Mutating public properties should typically not be done for non-primitive (object or array) properties. In other cases when an element needs to manage state, a private property set with the state: true option should be used. When needed, state properties can be initialized via public properties to facilitate complex interactions.

Returns the node into which the element should render and by default creates and returns an open shadowRoot. Implement to customize where the element's DOM is rendered. For example, to render into the element's childNodes, return this.

Node or ShadowRoot into which element DOM should be rendered. Defaults to an open shadowRoot.

Options used when calling attachShadow. Set this property to customize the options for the shadowRoot; for example, to create a closed shadowRoot: {mode: 'closed'}.

Details

Note, these options are used in createRenderRoot. If this method is customized, options should be respected if possible.

Memoized list of all element styles. Created lazily on user subclasses when finalizing the class.

static finalizeStyles(styles?): Array<CSSResultOrNative>

Permalink to finalizeStyles View source

Takes the styles the user supplied via the static styles property and returns the array of styles to apply to the element. Override this method to integrate into a style management system.

Parameters
styles?
CSSResultGroup
Details

Styles are deduplicated preserving the last instance in the list. This is a performance optimization to avoid duplicated styles that can occur especially when composing via subclassing. The last item is kept to try to preserve the cascade order with the assumption that it's most important that last added styles override previous styles.

Array of styles to apply to the element. The styles should be defined using the css tag function, via constructible stylesheets, or imported from native CSS module scripts.

Details

Note on Content Security Policy: Element styles are implemented with <style> tags when the browser doesn't support adopted StyleSheets. To use such <style> tags with the style-src CSP directive, the style-src value must either include 'unsafe-inline' or nonce-<base64-value> with <base64-value> replaced be a server-generated nonce. To provide a nonce to use on generated <style> elements, set window.litNonce to a server-generated nonce in your page's HTML, before loading application code:

enableUpdating(_requestedUpdate): void

Permalink to enableUpdating View source

Note, this method should be considered final and not overridden. It is overridden on the element instance with a function that triggers the first update.

Parameters
_requestedUpdate
boolean

firstUpdated(_changedProperties): void

Permalink to firstUpdated View source

Invoked when the element is first updated. Implement to perform one time work on the element after update.

Parameters
_changedProperties
Map<PropertyKey, unknown> | PropertyValueMap<any>

Map of changed properties with old values

Details

Setting properties inside this method will trigger the element to update again after this update cycle completes.

getUpdateComplete(): Promise<boolean>

Permalink to getUpdateComplete View source

Override point for the updateComplete promise.

Details

It is not safe to override the updateComplete getter directly due to a limitation in TypeScript which means it is not possible to call a superclass getter (e.g. super.updateComplete.then(...)) when the target language is ES5 (https://github.com/microsoft/TypeScript/issues/338). This method should be overridden instead. For example:

Is set to true after the first update. The element code cannot assume that renderRoot exists before the element hasUpdated.

True if there is a pending update as a result of calling requestUpdate(). Should only be read.

performUpdate(): void | Promise<unknown>

Permalink to performUpdate View source

Performs an element update. Note, if an exception is thrown during the update, firstUpdated and updated will not be called.

Details

Call performUpdate() to immediately process a pending update. This should generally not be needed, but it can be done in rare cases when you need to update synchronously. Note: To ensure performUpdate() synchronously completes a pending update, it should not be overridden. In LitElement 2.x it was suggested to override performUpdate() to also customizing update scheduling. Instead, you should now override scheduleUpdate(). For backwards compatibility with LitElement 2.x, scheduling updates via performUpdate() continues to work, but will make also calling performUpdate() to synchronously process updates difficult.

requestUpdate(name?, oldValue?, options?): void

Permalink to requestUpdate View source

Requests an update which is processed asynchronously. This should be called when an element should update based on some state not triggered by setting a reactive property. In this case, pass no arguments. It should also be called when manually implementing a property setter. In this case, pass the property name and oldValue to ensure that any configured property options are honored.

Parameters
name?
PropertyKey

name of requesting property

oldValue?
unknown

old value of requesting property

options?
PropertyDeclaration<unknown, unknown>

property options to use instead of the previously configured options

scheduleUpdate(): void | Promise<unknown>

Permalink to scheduleUpdate View source

Schedules an element update. You can override this method to change the timing of updates by returning a Promise. The update will await the returned Promise, and you should resolve the Promise to allow the update to proceed. If this method is overridden, super.scheduleUpdate() must be called.

Details

For instance, to schedule updates to occur just before the next frame:

shouldUpdate(_changedProperties): boolean

Permalink to shouldUpdate View source

Controls whether or not update() should be called when the element requests an update. By default, this method always returns true, but this can be customized to control when to update.

Parameters
_changedProperties
Map<PropertyKey, unknown> | PropertyValueMap<any>

Map of changed properties with old values

update(_changedProperties): void

Permalink to update View source

Updates the element. This method reflects property values to attributes. It can be overridden to render and keep updated element DOM. Setting properties inside this method will not trigger another update.

Parameters
_changedProperties
Map<PropertyKey, unknown> | PropertyValueMap<any>

Map of changed properties with old values

updateComplete: Promise<boolean>

Permalink to updateComplete View source

Returns a Promise that resolves when the element has completed updating. The Promise value is a boolean that is true if the element completed the update without triggering another update. The Promise result is false if a property was set inside updated(). If the Promise is rejected, an exception was thrown during the update.

Details

To await additional asynchronous work, override the getUpdateComplete method. For example, it is sometimes useful to await a rendered element before fulfilling this Promise. To do this, first await super.getUpdateComplete(), then any subsequent state.

updated(_changedProperties): void

Permalink to updated View source

Invoked whenever the element is updated. Implement to perform post-updating tasks via DOM APIs, for example, focusing an element.

Parameters
_changedProperties
Map<PropertyKey, unknown> | PropertyValueMap<any>

Map of changed properties with old values

Details

Setting properties inside this method will trigger the element to update again after this update cycle completes.

willUpdate(_changedProperties): void

Permalink to willUpdate View source

Invoked before update() to compute values needed during the update.

Parameters
_changedProperties
Map<PropertyKey, unknown> | PropertyValueMap<any>
Details

Implement willUpdate to compute property values that depend on other properties and are used in the rest of the update process.

Converts property values to and from attribute values.

Import

Methods and properties

fromAttribute(value, type?): Type

Permalink to fromAttribute View source

Called to convert an attribute value to a property value.

Parameters
value
null | string
type?
TypeHint

toAttribute(value, type?): unknown

Permalink to toAttribute View source

Called to convert a property value to an attribute value.

Parameters
value
Type
type?
TypeHint
Details

It returns unknown instead of string, to be compatible with https://github.com/WICG/trusted-types (and similar efforts).

Defines options for a property accessor.

Import

Methods and properties

readonly attribute?: string | boolean

Permalink to attribute View source

Indicates how and whether the property becomes an observed attribute. If the value is false, the property is not added to observedAttributes. If true or absent, the lowercased property name is observed (e.g. fooBar becomes foobar). If a string, the string value is observed (e.g attribute: 'foo-bar').

readonly converter?: AttributeConverter<Type, TypeHint>

Permalink to converter View source

Indicates how to convert the attribute to/from a property. If this value is a function, it is used to convert the attribute value a the property value. If it's an object, it can have keys for fromAttribute and toAttribute. If no toAttribute function is provided and reflect is set to true, the property value is set directly to the attribute. A default converter is used if none is provided; it supports Boolean, String, Number, Object, and Array. Note, when a property changes and the converter is used to update the attribute, the property is never updated again as a result of the attribute changing, and vice versa.

readonly noAccessor?: boolean

Permalink to noAccessor View source

Indicates whether an accessor will be created for this property. By default, an accessor will be generated for this property that requests an update when set. If this flag is true, no accessor will be created, and it will be the user's responsibility to call this.requestUpdate(propertyName, oldValue) to request an update when the property changes.

readonly reflect?: boolean

Permalink to reflect View source

Indicates if the property should reflect to an attribute. If true, when the property is set, the attribute is set using the attribute name determined according to the rules for the attribute property option and the value of the property converted using the rules from the converter property option.

readonly state?: boolean

Permalink to state View source

When set to true, indicates the property is internal private state. The property should not be set by users. When using TypeScript, this property should be marked as private or protected, and it is also a common practice to use a leading _ in the name. The property is not added to observedAttributes.

readonly type?: TypeHint

Permalink to type View source

Indicates the type of the property. This is used only as a hint for the converter to determine how to convert the attribute to/from a property.

hasChanged(value, oldValue): boolean

Permalink to hasChanged View source

A function that indicates if a property should be considered changed when it is set. The function should take the newValue and oldValue and return true if an update should be requested.

Parameters
value
Type
oldValue
Type

Map of properties to PropertyDeclaration options. For each property an accessor is made, and the property is processed according to the PropertyDeclaration options.

Import

A Map of property keys to values.

Import

Type

T ? PropertyValueMap<T> : Map<PropertyKey, unknown>

Details

Takes an optional type parameter T, which when specified as a non-any, non-unknown type, will make the Map more strongly-typed, associating the map keys with their corresponding value type on T. Use PropertyValues<this> when overriding ReactiveElement.update() and other lifecycle methods in order to get stronger type-checking on keys and values.