 The closed watcher API enables a consistent experience when handling closed requests. Easily implement an accordion pattern using the details element. Permission policy violation reports are now available. And there's plenty more. I'm Adriana Jara. Let's dive in and see what's new for developers in Chrome 120. An important feature of model or pop-up components is that they are easy to close, with a consistent mechanism for doing so. Those mechanisms are called closed requests. They are typically the escape key on desktop platforms and the back gesture or button on Android. Web developers had no good way to handle closed requests for their own components. This is especially problematic on Android devices, where providing the simple closing behavior for the back gesture was quite complex. This conversion brings the solution with closed watcher, a new API for directly listening and responding to closed requests. You can see an example on the screen. It also includes upgrades to dialogue and pop-over to use the new closed request framework, so that they respond to the Android back button. Check out the article in the description for the link to the code sample to try out closed watcher in your custom elements. The name attribute for the details element makes it easy to implement the accordion pattern using a sequence of details HTML elements. Multiple details elements that have the same name form a group. With this app, at most one element in that group can be opened at once. You can see it in action with the example on the screen where a group of details shares the name cookies. Check the link in the description for this easy implementation of the accordion pattern. Permissions policy violation reports are now available. These reports integrate the permissions policy API that allows developers to control the browser features available to a page, its iframes and sub-resources by declaring a set of policies for the browser to enforce with the reporting API, which provides a generic reporting mechanism for web applications to use and make reports available based on several platform features. These permissions policy API and reporting API integration allows web developers to configure endpoints to which permissions policy violation reports will be sent, allowing site owners to see when these allowed features are being requested for their pages in the field. The link in the description includes the documentation to implement permissions policy violation reports. And of course, there's plenty more. The relaxed CSS nesting implementation allows nested style rules to begin with an element. Rather than require the ampersand symbol in front or being wrapped with ease. With the enter picture-in-picture action in the media session API, websites can register an action handler, which can be used to open a picture-in-picture or document picture-in-picture window. And a reminder that Chrome is working towards deprecating third-party cookies. And there's going to be an experiment that could affect your website starting in January. So it's important that you check the article in the description for more information on auditing and mitigating steps. All the details, including links, docs, and specs are in the post linked in the description. Hit the subscribe button now so that you don't miss the latest Chrome DevTools video, GUI challenges, and more. Yo soy Adriana Jara. Our team wishes you happy holidays. And as soon as Chrome 121 is released, I'll be right here to tell you what's new in Chrome.