> One obvious problem I’m wondering about when ...

# webassembly

[andrew]

One obvious problem I’m wondering about when taking this approach, is the browser back button: if writing a stateful WebAssembly ‘Application’, then the browser back-button would, on the face of it, be like an ‘immediate quit’, losing all the App state and potentially ruining the UX. Is there a way to veto or intercept the back-button?