New in Chrome 119

Here's what you need to know:

• There’s an update to the expiration date upper limit for cookies already in storage.
• CSS has new pseudo-classes, relative color syntax and more.
• Fenced Frames added improvements like ad size macros and others.
• And there’s plenty more.

I’m Adriana Jara. Let’s dive in and see what’s new for developers in Chrome 119.

# Cookies expiration date.

Since Chrome 104 newly created cookies or those updated with an expiration date have had that date capped at no more than 400 days in the future. This same limit will now be retroactively applied to cookies already in storage.

The expiration dates of these cookies will be capped at no more than 400 days after the first time Chrome 119+ starts up and does a one time database migration. The impact of this change will not be felt by users until at least 400 days after Chrome 119 is released, and then only for existing cookies that have not been updated in that period.

You can read more about the expiration date recommendation and here is a friendly reminder that third party cookies will be deprecated in the near future and a guide to prepare for the deprecation.

# CSS updates

For CSS we have three updates:

Number one: the new :user-invalid and :user-valid pseudo-classes that represent an element with incorrect or correct input, respectively, but only after the user has significantly interacted with it. They are similar to the :valid and :invalid, pseudo-classes but with the added constraint that the new pseudo-classes only match after the user has interacted with the element.

Number two: the relative color syntax allows developers to define colors by modifying the parameters of other colors.

For example: oklab(from magenta calc(l * 0.8) a b); results in an Oklab magenta that is 80% lighter.

And number three: clip-path now supports more values.

The clip-path property creates a clipping region that sets what part of an element should be shown. Parts that are inside the region are shown, while those outside are hidden.

Now you can use <geometry-box> values to control the clip's reference box, making clip-path easier to use. These box values can be used alongside basic shapes (for example, clip-path: circle(50%) margin-box), or they can be used alone to clip to the specified box (for example, clip-path: content-box).

You can also use the functions xywh() and rect() that make it easier to specify rectangular or rounded-rectangular clips.

Correction: A previous version of this article referred to inprovements for Fenced Frames. These changes are now shipping in Chrome 120.

# And more!

Of course there’s plenty more.

• WebSQL is fully removed as of Chrome 119. A reverse origin trial allows developers to continue to use WebSQL until Chrome 123.

• Now the monitorTypeSurfaces option can be used to prevent the user from sharing an entire screen, with getDisplayMedia()

• There’s an origin trial that adds a fullscreen windowFeatures parameter to the window.open() JavaScript API to allow the caller to open a popup directly to full-screen.

# Further reading

This covers only some key highlights. Check the links below for additional changes in Chrome 119.

• What's new in Chrome DevTools (119)
• Chrome 119 deprecations and removals
• ChromeStatus.com updates for Chrome 119
• Chromium source repository change list
• Chrome release calendar

# Subscribe

To stay up to date, subscribe to the Chrome Developers YouTube channel, and you'll get an email notification whenever we launch a new video.

Yo soy Adriana Jara, and as soon as Chrome 120 is released, I'll be right here to tell you what's new in Chrome!