You're making a different argument than the GP. Mobile Safari already has this requirement and it works in a different way. The problem is that the Chrome tea

You're making a different argument than the GP. Mobile Safari already has this requirement and it works in a different way. The problem is that the Chrome team did it in a completely different way that broke everyone's expectations. It also didn't make any sense. Why would you require the dev to unpause the Context themselves? Why not just unpause it automatically once the user has interacted in the right way? And now that Chrome has moved, what if Edge and Firefox create their own 3rd and 4th standards. I have a library that was broken by this. It was an easy fix, but it was still headscratching that I needed to do anything. Like most libs, I was already complying with the mobile Safari way of doing things.