Right now, when compilation fails, the input code is simply echoed back in the output area. Let's display an error from TeX (or texvcjs) instead. This will require some collaboration with the backend, which will need to report errors in a standard fashion.
If the server is unreachable when the extension is loaded (indicated by the fonts request failint), the extension should just refuse to open. It can do nothing useful without a connection to the server.
Right now, when compilation fails, the input code is simply echoed back in the output area. Let's display an error from TeX (or texvcjs) instead. This will require some collaboration with the backend, which will need to report errors in a standard fashion.
If the server is unreachable when the extension is loaded (indicated by the fonts request failint), the extension should just refuse to open. It can do nothing useful without a connection to the server.