Install web apps with the new HTML install element

Post by llbbdd » Tue, Jun 02, 2026, 8:19 PM UTC

doublerabbit wrote: post #7

Browsers shouldn't have an install. Can we stop half-baked HTML XML syntax at this point? I forsee abuse of such: const button = document.querySelector('install'); button.addEventListener('promptdismiss', () => { console.log('User dismissed the install prompt but forcing installation of adware, malware and bitcoing mining anyway'); });

Post by Zardoz84 » Wed, Jun 03, 2026, 3:28 PM UTC

llbbdd wrote: post #13

Zardoz84 wrote: post #9

> the browser's control over the button's label text, language, and appearance means it can trust the user's click as a genuine signal of intent. Like we don't saw fake download bottons imitating the legitime button.

Prompting for installation opens a dialog controlled and populated by the browser that has the name and author of the app to be installed. You can test it on the example page here, linked from the article: https://microsoftedge.github.io/Demos/pwa-install-element/in...

Post by nixosbestos » Sun, Jun 07, 2026, 4:23 AM UTC

EffrafaxOfWug wrote: post #10

nixosbestos wrote: post #8

Since apparently this thread needs context, yes, you can install PWAs from Firefox on Android and I've heard it's returning to desktop. This just seems to be a way (in Chrome) to trigger the already existing PWA install flow but from some styles element on the page, rather than the user knowing how to trigger the install flow (usually multiple clicks). Edit: I wonder if you could do some click-jacking attacks here...

> can install PWAs from Firefox on Android The last time I checked firefox on android didn't support PWAs like Chrome does. It just creates a shortcut to your homescreen. Chrome on android use WebAPKs. You can verify this by looking at the package id in the app info of the created shortcut.