Here are some more funny examples:

There seems to be an internal check in Google Translate that tries to ensure that the output length is consistent with the input length, otherwise it will fall back to the old translation model. However, you can fool this check by padding your input with a bunch of dots.

Here is the link for the prompt used in the screenshot. Make sure you set the translation model to "advanced" rather than "classic." It seems to be the most reliable with the Japanese -> English translation mode.

translate.google.com?sl=ja&tl=en&...

I personally think the security risk with this is minimal. Chrome runs the JS in PDFs in a very limited version of V8 (without a JIT compiler or WASM support), so the JS interpreter should be pretty secure. The JS APIs are also super limited so there's not a whole lot a bad actor can do.

It's fixed now in the latest commit. Before, I had removed the screen melt animation because it blocks the main thread. In JS, if this happens, nothing on the screen can be updated, so effectively the game just froze for the duration of the animation.