workaround to access local storage from content_scripts

[quaz...@gmail.com]

I can't seem to access local storage from webextension. I don't get an error but the result is always empty.
Probably due to bug https://bugzilla.mozilla.org/show_bug.cgi?id=1197346

Someone in the bug conversation mentioned a workaround using messaging but I can't figure it out. I need an example of how to pull objects like values and arrays out of local storage from a content script via a background script using messaging, unless there is a better way.

[quaz...@gmail.com]

oh and by the way ... in case anybody reading this can fix ... this link ...
To learn much more about this, see the guide to messaging.
... on this page ...
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_scripts#Communicating_with_background_scripts
... is broken

[Dave Royal]

quaz...@gmail.com Wrote in message:

> I can't seem to access local storage from webextension. I don't get an error but the result is always empty.
> Probably due to bug https://bugzilla.mozilla.org/show_bug.cgi?id=1197346
>

That bug is reported to give an error. And it's reported fixed in
48, so not long to wait.
Are you using the same type of 'local storage'
as that bug?
There's the new webextensions storage.local and the old
localStorage, which does work in content scripts.

(Do these access the same data, BTW?)
--
(Remove any numerics from my email address.)

[quaz...@gmail.com]

I am using version 48 ... chrome.storage.local.get ... how do I use the new one? I'm using the ones in the webextension documentation.

I only have one set of data ... so I need to access it from options script, background script, and content script.

[Dave Royal]

quaz...@gmail.com Wrote in message:

> I am using version 48 ... chrome.storage.local.get ... how do I use the new one? I'm using the ones in the webextension documentation.
>
> I only have one set of data ... so I need to access it from options script, background script, and content script.
>

Comment #14
in that bug suggests there might be another bug for
use in options.

[quaz...@gmail.com]

The storage is working in options. Is there a separate storage for options and a separate storage for background and a separate storage for content_scripts?

[Dave Royal]

I have a Google Chrome extension which does chrome.storage.local.set in
options.js and then gets it in a content script. The get is async so I
had to put most of the subsequent code into the callback function. If you
don't do that I guess the option might be empty.

I haven't implemented this in Fx yet - I want Android support - so I
don't know if Fx would be the same, but I expect so.

[quaz...@gmail.com]

> I have a Google Chrome extension which does chrome.storage.local.set in
> options.js and then gets it in a content script. The get is async so I
> had to put most of the subsequent code into the callback function. If you
> don't do that I guess the option might be empty.

That's exactly what I need to do. I have confirmed the data I need is stored properly, I just can't seem to retrieve it from content_script. Would you care to share that part of your code?

[Dave Royal]

chrome.storage.local.get('MCnewPostScroll',function(items) {
newPostScroll = items['MCnewPostScroll'];
code that uses newPostScroll ;
});

Unlike my Fx (SDK) version of this the whole content script is within the
callback function.

[quaz...@gmail.com]

> chrome.storage.local.get('MCnewPostScroll',function(items) {
> newPostScroll = items['MCnewPostScroll'];
> code that uses newPostScroll ;
> });

Wow! That worked! Thanks!