Frontend Development 3 min read

Google Chrome 111 Introduces Improved Download UI, View Transitions API, Automatic Permission Revocation, and New Document Picture-in-Picture API

Chrome 111, released a month after Chrome 110, brings a refined download bubble UI, a numeric download count, smoother page transition support via the View Transitions API, automatic revocation of unused site permissions, and a new Document Picture-in-Picture API for richer web experiences.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
Google Chrome 111 Introduces Improved Download UI, View Transitions API, Automatic Permission Revocation, and New Document Picture-in-Picture API

One month after its predecessor, Google officially released Chrome version 111, which includes improvements to the "download bubble" user interface, an extended picture-in-picture API, and smoother transitions for web applications.

Improved Download Interface

Since Chrome 99 dramatically changed the download button, Google has been refining the download UI; the large download bar at the bottom of the screen has been replaced by a "download bubble" in the top toolbar.

Chrome 111 adds a numeric indicator showing how many items are currently being downloaded, a small but user‑friendly change.

Smoother Transitions

Web applications have always been a focus of Chrome updates. With Chrome 111, Google introduces a new View Transitions API that makes it easier for developers to implement smooth page‑to‑page transitions, making web apps feel more like native applications.

Although CSS can already provide animations and transitions, this API simplifies the process for developers.

Automatic Revocation of Site Permissions

Many websites request permissions such as location, notifications, clipboard, or camera, granting them indefinitely after a single approval.

Starting with Chrome 111, the browser will automatically revoke permissions for sites that have not been used or visited in the past two months.

Picture-in-Picture Mode

Chrome 111 is testing a new Document Picture-in-Picture API. With this API, the picture‑in‑picture window can contain any HTML content, not just video.

The new API builds on the previous Picture-in-Picture API, which only allowed HTMLVideoElement . This enhancement enables web developers to provide richer picture‑in‑picture experiences for their users.

frontend developmentChromePicture-in-Pictureweb APIsBrowser UpdatesView Transitions
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.