@ading.dev
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.
February 2, 2025 at 1:25 PM
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.
January 14, 2025 at 11:54 PM
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.