instal the new version for mac App Builder 2023.32

We also remove the support to add content and background scripts from the Files Manager for the same reason. We remove from the app object the methods that allow us to communicate with Web Extensions content scripts, since those methods have no sense anymore. We know that this represent a lose of functionality comparing to when we use the manifest version 2, however, the version 2 of the manifest files will be deprecated soon, and, therefore, we have no other option than the referred above: yes, we lose functionality, but, at least, can continue to deploy apps who will use the manifest version 3, of course, if we can go ahead with the referred limitations. This means that our apps, running as Web Extensions, cannot access the browser's local storage nor interact with the browser's page's content.

It's very important to note, that, with the introduction of the Web Extensions manifest version 3 and the impossibility to use the 'unsafe-eval' in the CSP (Content Security Policy) of this manifest version (which DecSoft App Builder apps need in order to use the VueJS runtime compiler), the DecSoft App Builder apps deployed as Web Extensions, must run now inside a kind of sandbox. We start to use the manifest version 3 when preparing the manifest files for the apps to be deployed as Web Extensions for modern browsers.

Instal the new version for mac App Builder 2023.32