Display Locking is an umbrella term of related features designed primarily to allow developers to increase performance of their sites. In addition, some of the features in the display locking project enable site behaviors that were not previously easy to accomplish (e.g. searchability in collapsed sections).
This document provides an overview of the features under the Display Locking projects with links that provide additional information.
`content-visibility is a CSS property designed to allow developers and browsers to easily scale to large amount of content and control when rendering work happens.
The spec draft for the feature is in a mature state.
The feature is currently implemented in Chromium M85 behind a --enable-blink-features=CSSContentVisibility flag.
content-visibility: hidden-matchable
content-visibility: hidden-matchable is an additional value for the
content-visibility property that allows user-agents to search for find-in-page
matches inside an otherwise hidden element. This feature is meant to be combined
with the beforematch event to allow searchability into collapsed sections
which expand if there is a match found.
This feature depends on both the successful adoption of content-visibility
feature as well as the beforematch event. The explainer outlines the target
use-cases, but neither the spec draft nor the TAG review are available at this
time.
This is currently implemented in Chromium M85 behind a --enable-blink-features=CSSContentVisibilityHiddenMatchable flag.
- spec draft -- not yet available.
- explainer
- TAG review -- not yet available.
containt-intrinsic-size is a CSS property that allows the developer to specify
an intrinsic size to use when size-containment is specified. This enables the
developers to specify "placeholder size" on content which is meant to be sized
by intrinsic sizing, but has size containment applied to it.
The spec draft for the feature is in a mature state.
The feature is currently implemented and shipped in Chromium M83.
beforematch is an event which is fired under one of the following conditions:
- There has been a find-in-page request with the matching text found inside the target element.
- There has been a scroll-to-text navigation with the text being found inside target element.
- There has been a fragment link navigation and the target element was the fragment target.
This allows pages to react to users searching for content on their sites. This
is particularly useful in combination with content-visibility: hidden-matchable
as it allows searchability inside otherwise hidden content.
The exact requirements and the design of this feature is still being discussed.
The feature is under development in Chromium M85 and is available behind the --enable-blink-features=BeforeMatchEvent flag.
- spec draft -- not yet available
- explainer
- TAG review
- privacy assessment
As the proposed features evolve, several competing API shapes might be considered at the same time, the decisions on particular behaviors might not be finalized, and some documentation may be out of date.
This document was last updated on May 28, 2020.