The bits shared between StaticRange and Range objects are put on a shared superclass named AbstractRange.

Motivation

According to the StaticRange.idl, there are some duplicate methods with Range. Create an AbstractRange superclass and move some of the methods on Range that we want on StaticRange to the superclass as well. StaticRange and Range both inherit from AbstractRange. To reclassify Range objects as "live ranges" rather than "ranges". this can be communicated more clearly to the user.

Specification

Specification link


Specification being incubated in a Community Group

Status in Chromium

Blink>DOM


Enabled by default (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

Owner

Last updated on 2021-05-23