2 ms·
In theory. At least firefox still allows playing audio via window.AudioContext without any user interaction. Audio isn't the only problem though. I'm starting
by account42 2y ago
In theory. At least firefox still allows playing audio via window.AudioContext without any user interaction.
Audio isn't the only problem though. I'm starting to think that any non-trivial javascript execution should be behind a permission prompt.
- jimbobthrowawy 2y agoBrowser vendors are rightfully scared of "breaking" websites. I don't know how you'd define non-trivial javascript in a way that couldn't be circumvented.
- account42 2y ago> I don't know how you'd define non-trivial javascript in a way that couldn't be circumvented. One approach would be to start out with the interpreter only with extreme throttling. Then to remove the throttling and enable the JIT you'd need explicit permissions.