Thomas Steiner 
Enhancements to the `<permission>` element: https://developer.chrome.com/blog/enhancements-to-permission-element. Chrome has an origin trial for a proposed new HTML element that lets you declaratively ask for permission to use APIs. Its core selling point is that it offers support for unblocking the user if they have accidentally declined a permission. It now offers fallback content and has icon support.
Enhancements to the proposed <permission> element  |  Blog  |  Chrome for Developers

The proposed permission HTML element is no longer void and also has support for icons.

Chrome for Developers
May 13, 2025 at 6:26amWeb
Show threadJeremy KeithMay 14, 2025

@tomayac Any chance you could amend that article to include the word “proposed” as in “the *proposed* `permission` element”?

Right now it reads as though this is an HTML element that you’d find in the spec, which as you know, given Apple and Mozilla’s stance, is not the case.

I really hope that the current wording is an oversight rather than deliberate sneakiness.

Show threadThomas Steiner May 14, 2025

@adactio It's actually the first sentence that implies that this is non-final: "The HTML <permission> element is still in origin trial, as the Chrome team refines it, building upon the foundation laid in our initial origin trial".

But I'm happy to make this read "The <ins>proposed</ins> HTML <permission> element is still in origin trial, as the Chrome team refines it, building upon the foundation laid in our initial origin trial", no worries at all.

Show threadThomas Steiner May 14, 2025
@adactio Title and first sentence updated. This should go live soon.
Show threadJeremy KeithMay 14, 2025
@tomayac Great! Thank you!
Show threadRobert Anderberg 🕹️May 15, 2025
@tomayac Awesome