Mariko Kosaka [X](https://twitter.com/kosamari)

<br />

[Video](https://www.youtube.com/watch?v=fSlNvBU-t38)

Here's what you need to know:

- [More CSS styling](https://developer.chrome.com/blog/new-in-chrome-131.md.txt#styling-details) for the `<details>` element.
- Easier print layout with [page margin boxes](https://developer.chrome.com/blog/new-in-chrome-131.md.txt#page).
- And there's plenty [more](https://developer.chrome.com/blog/new-in-chrome-131.md.txt#more).

I'm Mariko Kosaka. Let's dive in and see what's new for developers in Chrome 131.

> [!NOTE]
> **Note:** The initial version of this post included [CSS Highlight Inheritance](https://developer.chrome.com/blog/selection-styling.md.txt) which was removed as it caused some compatibility issues. The release of the feature is on hold pending a solution to the problem.

## Styling Improvements to `<details>` and `<summary>`

You now have more options to style the structure of the `<details>` and `<summary>` elements in order to build disclosure or accordion widgets.

The changes introduced in this release enable the use of the `display` property, and add a `::details-content` pseudo-element to style the part that expands and collapses.

Historically it was impossible to change the display type of the `details` element.
This restriction has now been relaxed, allowing you to use things like grid or flex layouts.

In this exclusive accordion example, made of several `details` elements, when one of the `details` elements is expanded, its content is placed next to the `summary`.

![Accordion widget with Flex layout](https://developer.chrome.com/static/blog/new-in-chrome-131/image/image3.jpg)

This is achieved by using a flex layout on the `details` element. You can also try more layout patterns with other display values such as `grid`.

Check out Bramus' article [More options for styling `<details>`](https://developer.chrome.com/blog/styling-details.md.txt) for a more in-depth explanation.

## `@page` margin boxes

Support for page margin boxes, when printing a web document, or exporting it as PDF, has been added.

Page margin boxes let you define the contents in the margin area of a page. So, you can provide custom headers and footers rather than using the built-in headers and footers generated by the browser.

The page margin is defined using the `@page` rule in CSS.

```css
@page :right {
  @bottom-left {
    content: "My book";
    font-size: 9pt;
    color: #333;
  }
}
```

The appearance and the contents of a margin box are specified with CSS properties inside the at-rules representing the 16 margin boxes using generated content.

For page numbering, counters are also supported with `page` for the current page number, and `pages` for the total number of pages.

Check out Rachel's article [Add content to the margins of web pages when printed using CSS](https://developer.chrome.com/blog/print-margins.md.txt) for a more in-depth explanation.

## And more!

And of course there is plenty more.

- Support for external SVG resources for 'clip-path', 'fill', 'stroke' and 'marker'.
- WebHID is enabled inside dedicated worker contexts.
- Control the behavior of Emoji with the `font-variant-emoji` CSS property.

## Further reading

This covers only some key highlights. Check the following links for additional
changes in Chrome 131.

- [Release notes for Chrome 131](https://developer.chrome.com/release-notes/131.md.txt).
- [What's new in Chrome DevTools (131)](https://developer.chrome.com/blog/new-in-devtools-131.md.txt)
- [Chromium source repository change list](https://chromium.googlesource.com/chromium/src/+log/130.0.6723.92..131.0.6778.33)
- [Chrome release calendar](https://chromiumdash.appspot.com/schedule)

## Subscribe

To stay up to date, [subscribe](https://goo.gl/6FP1a5) to the
[Chrome Developers YouTube channel](https://www.youtube.com/user/ChromeDevelopers/),
and you'll get an email notification whenever we launch a new video.

I'm Mariko Kosaka, and as soon as Chrome 132 is released, we'll be right here to
tell you what's new in Chrome!