Thomas Steiner

> emulate bold if you really want to. The spec should discourage this. It's a huge pain for screen reader users and definitely not 𝗙𝗨𝗡 to listen to. Try it...

Thank you very much for opening the issue. I actually was purely focusing on masking, _not_ validating. What part of the explainer made you think it was also aimed at...

> > helps users enter information in forms more correctly, and existing data can be formatted adequately > > That's what I call 'validation' where you ensure the input characters...

Sorry, yes, I realized this as well, which is why I deleted the comment. I guess it really boils down to `try..catch`ing.

(Deep link for said pattern: https://web.dev/patterns/advanced-apps/share/.)

This seems especially desirable in the context of [crbug/1446327](https://crbug.com/1446327), which is about the PiP window disappearing after the computer was locked.

(I searched the spec for "move", but didn't find anything. The relevant search term would have been "position".) For people following this, the relevant spec section is [this](https://wicg.github.io/document-picture-in-picture/#:~:text=The%20website%20cannot%20set%20the%20position%20of%20the%20PiP%20window.): > The...

I love the user case. This is more of a browser support request than a spec issue, though. For Chrome, the Async Clipboard API is being worked on in the...

> It would be nice to speak based on the specification rather than Chromium implementation here, for the interop sake. The spec makes no assumptions as to the supported formats,...

> There are [mandatory/optional types](https://w3c.github.io/clipboard-apis/#mandatory-data-types-x) so I see at least some level of assumption. This issue can be read as a request to add a new item in the list....