Mossroy

It should be possible to do that by adding an error callback to the functions (just like we have callbacks to return the results) Another option would be to change...

Now that we have merged #804 (and several other ones), you can tackle this one and #841 The goal is to remove the requirejs dependencies on uiUtil from the following...

Regarding *dec_wrapper.js, here is a possible solution: We could store the *MachineType and error messages in variables of each *dec_wrapper.js. It's already the case for *MachineType: only the error message...

> > In app.js, we could add some code that runs on startup, and reads the *MachineType of each wrapper. If it's null, it should try again one second later...

> > you would pass a lambda function > > @mossroy By this, do you mean an anonymous function? Because being on ES5 we can't use arrow functions I suppose....

> Also, the `ZIMArchive` function (which uses `uiUtil.systemAlert`) defined in `zimArchive.js` is not called by `app.js` directly (In fact `app.js` doesn't depend on `zimArchive.js` at all ). It's being called...

I reopen this, because there are still the *dec_wrapper.js to handle

It's true in jQuery mode. I don't think we can have a reliable way to know if a file should be downloaded or displayed. Because it depends not only on...

Thanks @Jaifroid for your support and for taking the time to answer in detail all issues, even when they contain hasty criticism. The lack of ServiceWorker support in Firefox extensions...

I've implemented what I felt was necessary for that : passing all the files to the wasm, and call the libzim with the baseName (.zim instead of .zimaa). But every...