Chrome 110, scheduled for launch on February 7, 2022, includes a Web Share API handling change that improves privacy and security by requiring the Web Share API to explicitly allow third-party content.
This may not be something a single publisher needs to respond to.
It’s probably more relevant on the developer side, where they build things like web apps that use the Web Share API.
Still, it’s good to know what it is for the rare situation where it might come in handy in diagnosing why a website isn’t working.
The Mozilla developer page describes the Web Share API:
“The Web Share API allows a website to share text, links, files, and other content to user-selected sharing targets, using the underlying operating system’s sharing mechanisms.
These sharing destinations typically include the system clipboard, email, contacts or messaging applications, and Bluetooth or Wi-Fi channels.
…Note: This API should not be confused with the Web Share Target API, which allows a website to specify itself as a share target.”
allow=”web-share” attribute
An attribute is HTML markup that modifies an HTML element in some way.
For example, the nofollow attribute modifies the anchor element by signaling to search engines that the link is not trusted.
The