With this setting set, in the add-on debug console, the error disappears and the string “loaded” is displayed. So after loading the extension, I’ve went to about:addons and allowed the extension to run in private windows. I do however have an observation regarding this issue.Įxtensions, by default, are not allowed to run in private browsing and the bug report particularly states that the browser will be run in private browsing mode after modifying the settings in Step 1 of the STR. XULStore.jsm:66:15 is not displayed in the add-on debug console as with the other tested versions of the browser, however, the code is not executed. I’ve also reproduced the issue on the 79.0 Release version of the browser (79.0/20200720193547) as originally reported.Īs mentioned, I’ve managed to only partially reproduce the issue on the latest Nightly as the error Error: Can’t find profile directory. I’ve managed to fully reproduce the issue based on the provided STR on the latest Beta (81.0b4/20200829200810) and Release (80.0/20200818235255) and partially reproduce on the latest Nightly (82.0a1/20200830213209) under Windows 10 Pro 64-bit and Ubuntu 16.04 LTS. The attached test extension's code should have been executed, and no error message should have been displayed in the console.
Load resource://gre/modules/XULStore.jsm:66
This error message is shown in the console:Įrror: Can’t find profile directory. it's shown in the list of temporary add-ons. The attached test extension is loaded, i.e. (which Firefox automatically changes to “Use custom settings for history -> Always use private browsing mode” after restarting)
0 kommentar(er)
