https://github.com/WICG/layout-instability

A proposal for a Layout Instability specification
https://github.com/WICG/layout-instability

Last synced: 3 months ago
JSON representation

A proposal for a Layout Instability specification

• Host: GitHub
• URL: https://github.com/WICG/layout-instability
• Owner: WICG
• License: other
• Created: 2019-05-13T15:40:56.000Z (over 5 years ago)
• Default Branch: main
• Last Pushed: 2024-01-24T08:05:04.000Z (10 months ago)
• Last Synced: 2024-07-30T15:22:51.733Z (4 months ago)
• Language: Makefile
• Homepage: https://wicg.github.io/layout-instability/
• Size: 302 KB
• Stars: 160
• Watchers: 20
• Forks: 26
• Open Issues: 29
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE.md
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

• awesome-pagespeed-metrics - Spec - Layout Instability API - W3C

README

        
## Explainer: Layout Instability Metric

### Overview

Many websites suffer from **layout instability** - DOM elements shifting around

due to content loading asynchronously.

We propose a way for the user agent to measure layout instability during a

browsing session to compute "layout shift scores", which would be exposed by a

new interface in the

[Performance API](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API).

### Layout Shift Score

Each animation frame (a.k.a.

"[rendering update](https://html.spec.whatwg.org/#update-the-rendering)")

computes a **layout shift (LS) score** approximating the severity of visible

layout instability in the document during that frame.  An animation frame with

no layout instability has an LS score of 0.  Higher LS scores correspond to

greater instability.

The LS score is based on a set of [shifting nodes](#Shifting-Nodes) and two

intermediate values, the [impact fraction](#Impact-Fraction) and the

[distance fraction](#Distance-Fraction).

### Shifting Nodes

A **shifting node** is a DOM node whose visual representation starts in a

different location than it did in the previous animation frame for a reason

other than [transform change](#Transform-Changes) or [scrolling](#Scrolling).

"Starts" refers here to the node's

[flow-relative](https://www.w3.org/TR/css-writing-modes-4/#flow-relative) offset - for

example, its top left corner in a horizontal left-to-right writing mode.

The visual representation of a node is the space occupied by its

[box fragments](https://drafts.csswg.org/css-break-4/#fragment)

(for elements) or [line boxes](https://www.w3.org/TR/css-text-3/#line-breaking) (for text nodes).

Note that:

* A node that changes in size (for example, by having children appended),

  but starts at the same offset, is not a shifting node.

* A node whose start location changes two or more times during the same

  animation frame (for example, from

  [forced synchronous layouts](https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid_forced_synchronous_layouts)),

  but is ultimately painted at the same location as the previous frame, is not

  a shifting node.

### Transform Changes

Changing an element's [transform](https://developer.mozilla.org/en-US/docs/Web/CSS/transform)

affects its visual representation.  However, because

* transform changes don't reflow surrounding content,

* transform changes are a common target of fluid animations, and

* animated transform changes are easily rendered with hardware-accelerated

  compositing on a separate thread from the browser's layout and script

  execution tasks,

the layout instability metric doesn't treat transform-changing elements, or

their descendants, as shifting elements (unless their layout is affected in some

other way at the same time).

### Scrolling

To be a shifting node, the start location must change relative to the document

origin, the viewport, and every containing scrollable area.  This ensures that

* scrolling a simple element doesn't produce a layout shift

  (though this changes its location relative to the viewport);

* scrolling with a `position: fixed` element doesn't produce a layout shift

  (though this changes the fixed element's location relative to the document origin); and

* scrolling an `overflow: scroll` container doesn't produce a layout shift

  (though this changes the locations of descendant elements

  relative to both the viewport and the document origin).

### Impact Fraction

The **impact region** of an animation frame is the geometric union of the

previous-frame and current-frame visual representations, intersected with the

viewport, of all shifting nodes in that frame.

The **impact fraction** of an animation frame is the fraction of the viewport that

is occupied by the impact region.

![Illustration of a shifting element on a device, with the impact region

highlighted](https://i.imgur.com/XN7xdKF.png)

*Example: An element which occupies half the viewport shifts by a distance equal

to half its height.  The impact fraction for this animation frame is 0.75.*

### Distance Fraction

The **move distance** of a shifting node is the distance it has moved on

the horizontal or vertical axis (whichever is greater), relative to the viewport.

The **distance fraction** of an animation frame is the greatest move distance

of any shifting node in that frame, divided by the width or height

(whichever is greater) of the viewport.

![Illustration of shifting elements on a device, with their move distances

indicated by arrows](https://i.imgur.com/qeks8UK.png)

*Example: The most-shifted element moved a distance of one quarter of the

viewport.  The distance fraction for this animation frame is 0.25.*

The intent of incorporating the distance fraction into the LS score calculation

is to avoid overly penalizing cases where large elements shift by small

distances.

### LS Score Calculation

The layout shift (LS) score is equal to the impact fraction multiplied by the

distance fraction.

### Performance API

Animation frames with non-zero LS scores will notify a registered

[PerformanceObserver](https://w3c.github.io/performance-timeline/#the-performanceobserver-interface).

The observer's callback receives one or more `LayoutShift` entries:

```idl

interface LayoutShift : PerformanceEntry {

    double value;

    boolean hadRecentInput;

    DOMHighResTimeStamp lastInputTime;

    sequence sources;

};

```

The entry's `value` attribute is the LS score.  Its

[entryType](https://w3c.github.io/performance-timeline/#dom-performanceentry-entrytype)

attribute is `"layout-shift"`.

The `hadRecentInput` and `lastInputTime` attributes are described in

[Recent Input Exclusion](#Recent-Input-Exclusion).

The `sources` attribute is described in [Source Attribution](#Source-Attribution).

### Cumulative Scores

The user agent can compute a **document cumulative layout shift** (DCLS) score

as the sum of the document's LS scores for each animation frame that has occurred

during the browsing session.  The DCLS score is 0 when the document begins

loading, and grows whenever layout instability occurs.  The DCLS score does not

account for layout instability inside descendant browsing contexts, such as

those created by `` elements.

The user agent can compute a **cumulative layout shift** (CLS) score for a

[top-level browsing context](https://html.spec.whatwg.org/multipage/browsers.html#top-level-browsing-context)

by summing the LS scores of the top-level browsing context to the weighted LS

scores of its descendant browsing contexts.  In performing this aggregation,

the LS score of a layout shift in an `` should be weighted by the

fraction of the top-level viewport the `` occupies at the time the

layout shift occurs.

The DCLS and CLS scores are not directly exposed by the [Performance API](#Performance-API),

but we hope to make it easy for developers to construct these from the LS scores.

### Recent Input Exclusion

In calculating DCLS and CLS scores, developers and user agents may wish to

exclude LS scores from animation frames that occur after recent

[UI events](https://www.w3.org/TR/uievents/) events such as taps, key presses,

and mouse clicks.  This allows the page to modify its layout in response to

the event.

To facilitate this exclusion, the `LayoutShift` entry has attributes

indicating when such input last occurred, and whether it should be considered

"recent" for the purpose of the exclusion.

The `hadRecentInput` attribute is `true` when the last input occurred within

the past 500 ms.  It should be treated as a hint to ignore the layout shift in

calculating the DCLS and CLS scores.  This threshold was chosen to allow the

page to make asynchronous rendering updates as a result of the input, as long

as they occur without excessive delay. Developers wishing to implement a

different threshold can do so by examining the `lastInputTime`.

Events caused by pointer movement or scrolling do not count as "input" for the

purpose of the recent input exclusion and the input-related attributes on the

`LayoutShift` entry.

### Source Attribution

_NOTE: The `sources` attribute is currently only available in Chrome 84+ with

"Experimental Web Platform features" enabled (chrome://flags)._

On a complex website, it can be difficult to understand the cause of a high

CLS score given only the numeric values in the `value` attribute of the

`LayoutShift` entries.

To aid that effort, the `sources` attribute connects the `LayoutShift`

back to the specific DOM elements that experienced the shift.  This gives

the developer more insight into the causes of layout instability on their site.

The `sources` attribute is an array of up to 5 `LayoutShiftAttribution` objects:

```idl

interface LayoutShiftAttribution {

    Node node;

    DOMRect previousRect;

    DOMRect currentRect;

};

```

Each attribution contains a reference to a [shifted](#Shifting-Nodes) DOM node

along with rects that describe its visual representation in the viewport

before and after the shift.

#### Prioritization by Impact

Many nodes may shift in a single animation frame, but the user agent

selects no more than 5 to attribute in `sources`, and tries to avoid

redundancy. The method of selection follows these principles:

* If two nodes have shifted, and one fully contains the other (visually), only

  the larger node is attributed.  This means for example that if a container node

  shifts, we would not generally need to attribute all of its descendants,

  even though they too have shifted.

* If, after the elimination described above, there are still more than 5 shifted

  nodes eligible for attribution, they are prioritized by the size of their

  contribution to the [impact region](#Impact-Fraction).  That is, nodes

  occupying a greater area within the viewport are preferred.

We limit the number of attributions to 5 for the following reasons:

* In a large DOM, many nodes may shift at once, and it may be infeasible

  for user agents to report the full set of shifted nodes in a performant way.

* It may be cumbersome for developers to receive the full set of shifted nodes,

  and would encourage them to write non-performant code to examine such a set.

* Given the hierarchical nature of DOM, surfacing a small number of high level

  shifted elements is usually sufficient to understand the cause of layout

  instability.  Limiting to 5 with prioritization improves the signal to noise

  ratio of the report.

#### Caveat: Causality

It is possible that the true "root cause" of instability will be only

indirectly related to the DOM element that experiences a layout shift.

For example, if a newly inserted element shifts content below it,

the `sources` attribute will report only the shifted elements,

and not the inserted element.

We do not believe it is feasible for the user agent to understand

causes of instability at the level of indirection necessary

for a meaningful "root cause" attribution. However, we expect that

the more straightforward reporting of shifted elements in `sources`

will nevertheless be of significant value to developers

who are attempting to diagnose an occurrence of layout instability.

#### Specification

The updates to the Layout Instability API specification to incorporate

and explain the `sources` attribute are tracked in

[issue #11](https://github.com/WICG/layout-instability/issues/11).

### Computing DCLS with the API

The developer can compute the DCLS score by summing the LS scores:

```javascript

addEventListener("load", () => {

    let DCLS = 0;

    new PerformanceObserver((list) => {

        list.getEntries().forEach((entry) => {

            if (entry.hadRecentInput)

                return;  // Ignore shifts after recent input.

            DCLS += entry.value;

        });

    }).observe({type: "layout-shift", buffered: true});

});

```

By passing `buffered: true` to

[observe](https://w3c.github.io/performance-timeline/#dom-performanceobserver-observe),

the observer is immediately notified of any layout shifts that occurred before

it was registered.  (Layout shift entries are *not* available from the

[Performance Timeline](https://w3c.github.io/performance-timeline/#performance-timeline)

through `getEntriesByType`.)

A "final" DCLS score for the user's session can be reported by listening to the

[visibilitychange event](https://developers.google.com/web/updates/2018/07/page-lifecycle-api#event-visibilitychange),

and using the value of `DCLS` at that time.

A [demo page](https://output.jsbin.com/zajamil/quiet) illustrating the use of this

code can be viewed in Chrome 76+ with the command-line flag

`--enable-blink-features=LayoutInstabilityAPI`, or in Chrome 73-75 with the

command-line flag `--enable-blink-features=LayoutJankAPI`.

### Limitations

The presence of "layout instability" as defined by this metric correlates

imperfectly with the user experience of "jumpy" websites.

It's possible for a website to seem jumpy, but score well on CLS.  For example,

rebuilding the DOM with entirely new elements does not trigger a layout shift.

Conversely, it's possible for a website to provide a smooth user experience, but

score poorly on CLS.  For example, an image carousel that animates a layout

property such as [`left`](https://developer.mozilla.org/en-US/docs/Web/CSS/left)

will produce a layout shift on every frame of the animation.  (Carousel authors

should use [`transform`](https://developer.mozilla.org/en-US/docs/Web/CSS/transform)

instead, which avoids the layout shift, and also enables off-thread accelerated

compositing.)

The metric tries to make some allowances ([transform changes](#Transform-Changes),

[recent input](#Recent-Input-Exclusion)) for visual updates that are not likely

to negatively impact the user experience.  But these are in essence heuristics,

and not guaranteed to work well in every case.

### Precision, Variance, and Evolution

We provide a reasonably precise method of computing scores for layout instability,

but the score remains an [approximation](#Limitations) of the user experience.

We expect developers to use the score as a signal, and not to rely on its exact

numeric value in a manner such that the correctness of their page would be impacted

by a minor deviation in it.

The user agent may trade off precision for efficiency in the computation of

LS scores.  It is intended that the LS score have a correspondence to the

perceptual severity of the instability, but not that all user agents produce

exactly the same LS scores for a given page.

We expect the definition of the layout instability metric to evolve over time;

it should not be considered "frozen" merely because a spec has been produced.

We hope that such evolution can occur with sufficient cooperation between

implementers, so that browsers do not vary so significantly that developers

must choose between optimizing for one implementation over another.

### Privacy and Security

Layout instability bears an indirect relationship to resource timing, as slow

resources could cause intermediate layouts that would not otherwise be

performed.  Resource timing information can be used by malicious websites for

statistical fingerprinting.

The layout instability API only reports layout shifts in the current browsing

context (frame).  It does not directly provide the CLS score incorporating

subframes.  Developers can implement such aggregation manually, but browsing

contexts with different

[origins](https://html.spec.whatwg.org/multipage/origin.html#concept-origin)

would need to cooperate to share LS scores.

### Terminology

The "layout instability metric" was previously called the "layout stability

metric".

"Layout instability" and "layout shift" were previously referred to as

"layout jank".  The impact region was previously referred to as the "jank

region".  The LS score was previously referred to as the "jank fraction".

The DCLS score and CLS score were previously referred to as

"(aggregate) jank score".

The LayoutShift interface was previously implemented as PerformanceLayoutJank.

Its "value" attribute was previously named "fraction", and its entryType was

previously "layoutJank".

The layout instability API is an extension of the web performance API, but it is

not related to the speed or timing of layout computation.

### Links

* [Chrome Feature Dashboard Entry](https://www.chromestatus.com/feature/5110682739539968)

* [Blink Intent to Implement](https://groups.google.com/a/chromium.org/d/msg/blink-dev/jF1-M8KWAMU/ubGV4Fx2BgAJ)

* [Chromium Tracking Bug](https://crbug.com/581518)