Jeremy Tuloup

> This seems to be reproducible with a plain Playwright self-contained example, so I opened [microsoft/playwright#32542](https://github.com/microsoft/playwright/issues/32542). This doesn't look like it's going to be fixed upstream any time soon, so...

cc @martinRenou @DerThorsten since this came up a few times in prior discussions

More thoughts about this. We could imagine something like the following, which could be implemented in the kernel extensions directly: - the kernel worker catches calls to `console.log`, `console.error` and...

FYI @martinRenou implemented a first version in `jupyterlite-xeus` in https://github.com/jupyterlite/xeus/pull/197. The part implemented as a regular JupyterLab extension could likely be extracted from that repo, so it can be reused...

FYI I've started looking into extracting the plugin responsible for showing the logs from https://github.com/jupyterlite/xeus. So it can be used with the Pyodide kernel as well. Draft PR: https://github.com/jupyterlite/pyodide-kernel/pull/177 Quick...

After exploring this a bit more, it's starting to feel like using the built-in Log Console in JupyterLab may offer a more coherent UX when it comes to finding kernel...

Feedback from @lesteve for what would be useful to users, in order of priority: - this could take the form of a notebook toolbar item, next to the existing kernel...

Thanks @lesteve for testing and the feedback! > In the following snapshot, messages like "loading sqlite3" are shown in the JupyterLite widget but not the browser console. This is likely...

> In both cases it's the responsibility of the kernel to surface logs. So maybe we can look into this more over in https://github.com/jupyterlite/pyodide-kernel? Also if you feel like opening...

So a possible solution to this could be a dialog with a couple of checkboxes for files and settings. Something more advanced would list the files that have been modified,...