# Google Chrome 142

- Product: Google Chrome (https://whatsnew.fyi/product/google-chrome)
- Vendor: Google
- Date: 2025-10-28
- Version: 142
- Original notes: https://developer.chrome.com/release-notes/142
- Permalink: https://whatsnew.fyi/product/google-chrome/releases/142

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **changed** — ::view-transition element now uses position: absolute instead of position: fixed
- **added** — document.activeViewTransition property to represent the active view transition object or null if no transition is ongoing
- **added** — :target-before and :target-after pseudo-classes to match scroll markers before or after the active marker
- **added** — Range syntax for style container queries and if() function to support comparison operators for custom properties
- **added** — interestfor attribute on <button> and <a> elements to trigger actions on target elements when user shows interest
- **changed** — select element rendering modes for mobile and desktop parity with size and multiple attributes
- **added** — Support for download attribute in SVG <a> element
- **added** — WebGPU primitive_index feature to expose a per-primitive index to fragment shaders
- **added** — WebGPU texture formats tier1 and tier2 with extended capabilities for render attachment, blending, multisampling, resolve and storage_binding

Stable release date: October 28th, 2025
Unless otherwise noted, the following changes apply to Chrome 142 stable channel release for Android, ChromeOS, Linux, macOS, and Windows.
##### CSS and UI
###### Absolute positioning for the ::view-transition element
View transitions use a pseudo subtree of the element, with ::view-transition being the root of that transition. Previously, the ::view-transition element was specified to have position: fixed. The CSS Working Group resolved to make this position: absolute and so Chrome now reflects that change.
This change shouldn't be noticeable because this element's containing block remains the snapshot containing block in either the absolute or fixed case. The only noticeable difference is in getComputedStyle.
Tracking bug #439800102 | ChromeStatus.com entry | Spec
###### activeViewTransition property on document
The View Transitions API lets developers start visual transitions between different states. The primary SPA entry point is startViewTransition(), which returns a transition object. This object contains several promises and functionality to track transition progress, and lets you manipulate transitions, for example, by skipping the transition or modifying its types.
From Chrome 142, developers no longer need to store this object. A document.activeViewTransition property represents this object, or null if no transition is ongoing.
This also applies to MPA transitions, where the object is only available through pageswap and pagereveal events. In this update, document.activeViewTransition is set to this object for the duration of the transition.
Tracking bug #434949972 | ChromeStatus.com entry | Spec
###### :target-before and :target-after pseudo-classes
These pseudo-classes match scroll markers that are before or after the active marker (matching :target-current) within the same scroll marker group, as determined by flat tree order:
- :target-before: Matches all scroll markers that precede the active marker in the flat tree order within the group.
- :target-after: Matches all scroll markers that follow the active marker in the flat tree order within the group.
Tracking bug #440475008 | ChromeStatus.com entry | Spec
###### Range syntax for style container queries and if()
Chrome enhances CSS style queries and the if() function by adding support for range syntax.
It extends style queries beyond exact value matching (for example, style(--theme: dark)). Developers can use comparison operators (such as > and <) to compare custom properties, literal values (for example, 10px or 25%), and values from substitution functions like attr() and env(). For a valid comparison, both sides must resolve to the same data type. It is limited to the following numeric types: <length>, <number>, <percentage>, <angle>, <time>, <frequency>, and <resolution>.
Tracking bug #408011559 | ChromeStatus.com entry | Spec
###### Interest Invokers (the interestfor attribute)
Chrome adds an interestfor attribute to <button> and <a> elements. This attribute adds "interest" behaviors to the element. When a user "shows interest" in the element, actions are triggered on the target element, for example, showing a popover. The user agent detects when a user "shows interest" in the element through methods such as holding the pointer over the element, hitting special hotkeys on the keyboard, or long-pressing the element on touchscreens. When interest is shown or lost, an InterestEvent fires on the target, which has default actions for popovers, such as showing and hiding the popover.
Tracking bug #326681249 | ChromeStatus.com entry | Spec
###### Mobile and desktop parity for select element rendering modes
By using the size and multiple attributes, the <select> element can be rendered as an in-page listbox or a button with a popup. However, these modes don't have consistent availability across mobile and desktop Chrome. In-page listbox rendering is unavailable on mobile, and a button with a popup is unavailable on desktop wh

_[Truncated at 4000 characters — full notes: https://developer.chrome.com/release-notes/142]_