All of my debugging process are done in:
- Windows 10
b.17134 - Firefox Developer Edition
v.68 x64 - The Internet connection is stable.
My extension is about saving settings and working on internationalization. Which leads to these 3 APIs that don’t working properly:
For the internationalization, I can pretty sure that it is a bug, because I do exactly what the guide told me to. The result only changes extension’s title and description. Anything, involves to Js i18n API, isn’t working. To ensure that it is not my fault, I cloned the guide ext used in the video. It got a same problem. Should I report this bug (is it even considered as a bug)?
About storage, I use it for option_ui. And I only used browser.storage.sync. The out-come is unidentified, literally. I use chain-function .then() to get the status of syncing and I get is success but nothing returns but unidentified, not even a tiny bug. So I guess the problem is due to unable to simulate the syncing process. So I decided to use examples Favourite colour and forget-it to test my case. In the example, things went to the same problem like I do, but, browser.storage.managed returns 2 errors:
Managed storage manifest not found
error occurred while processing 'sources: TypeError: can't access dead object
Stack: webExtensionTargetPrototype._allowSource@resource://devtools/server/actors/targets/webextension.js:292:5
TabSources/this.allowSource@resource://devtools/server/actors/utils/TabSources.js:25:39
_addSource@resource://devtools/server/actors/thread.js:1652:23
onSources@resource://devtools/server/actors/thread.js:1090:12
onPacket@resource://devtools/server/main.js:1291:58
receiveMessage@resource://devtools/shared/transport/child-transport.js:66:16
Line: 292, column: 5
In the forget-it example, thing went perfectly well with browser.storage.local. This makes my theory seems right enough.
So, with 1 bug and 1 unavoidable problem, what should I do? The storage is an important key to keep working on the other part of my extension.