This change removes the requirement for the "clipboard-read" permission when using the Async Clipboard API from within a "paste" event handler. It also applies to writing to the clipboard inside a "copy" or "cut" event, although writing plain text to the clipboard was already permitted on ANY user gesture, so this is a less notable change. Browser vendors differ in the details of how they permit access to the Async Clipboard API, but this change brings Chromium into alignment with other vendors and the specification [1] which states that read access is to be permitted when > the current script is running as a result of user interaction with a "Paste" element created by the user agent or operating system. [1] https://www.w3.org/TR/clipboard-apis/
Reduce permission fatigue and align behavior to long-standing user expectations by reducing the number of occasions that permissions are used (requested, required, displayed) during normal interaction (use of clipboard shortcuts).