Juho Forsén

@Willyfrog this is the UA string bug again, right? We patched the popup window, but the main window still uses the custom UA string that breaks Jitsi?

I can have a look tomorrow if you like, since I've already worked on both this plugin and Jitsi stuff in the desktop app.

This would be the cause: https://github.com/electron/electron/issues/16513

I don't think it's fixed in v8 either. As for the preload polyfill, that won't work in an iframe unless you set `nodeIntegrationInSubFrames` to `true` and that doesn't seem like...

Oh and this also fixes #25, obviously.

Some additional notes: - The default repository is `https://chrome-infra-packages.appspot.com/p/` - Package names are case-sensitive - The OS and architecture of a package is specified with a `/-` suffix. For PURL...

@mickmister following up on our brief chat yesterday, what's missing to get this merged? Just the QA review? cc @DHaussermann

Thanks @ylemkimon! I'll leave this issue open so you can use it to track updating the security policy. But if you'd rather create a separate ticket for that, feel free...

Workaround: rendering directly to a DOM element triggers the crash but rendering to a string and then assigning it to the same element's `innerHTML` doesn't.

> KaTeX can't write to innerHTML itself, at least in the renderToString interface (and in general when server-side rendering). There's no need to. This only affects `render`, and only when...