* This release of the product incorporates a "" file which is used while we are debugging our apps (F9). The same minor changes has been made also in some of the DecSoft app plugins included out of the box with the product. * Some minor changes has been made in some DecSoft App Builder controls in order to avoid some warnings while debugging our apps using the new "" file. It's a pain when we lose functionality in our product, however, we can take the option to remove the support for Web Extensions at all, and, on the contrary, we work hard in order to keep their support, even with the referred limitations. We encourage you to be ready with the manifest version 3, since the version 2 of the manifest files will be deprecated soon (they are already deprecated at the Chrome Web Extensions store). You can find this special release by login into your DecSoft customer area at our web site, and then navigate to the Releases tab -> DecSoft -> App Builder -> Web Extensions manifest version 2. We leave a special previous release of DecSoft App Builder for our customers who want to continue using the Web Extensions manifest version 2 and their related stuff. We also remove the app events that are intended to use with this kind of Web Extensions. We also remove from the product help the stuff which is related with the previous support of Web Extensions with manifest version 2. We also remove the WebExtensions samples apps, since they are prepared to run with the manifest version 2. 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.
0 kommentar(er)
