Home/ Questions/Q 7579575
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T17:42:43+00:00

I read Google Chrome Extensions Developer’s Guide carefully, it told me to save options

  • 0

I read Google Chrome Extensions Developer’s Guide carefully, it told me to save options in localStorage, but how is content_scripts able to get access to these options?

Sample:

I want to write a script for a couple of domains, and this script should share some options on these domains.

content_scripts:

//Runs on several domains
(function(){
    var option=getOptions();
    //Get options which have been set in options.html
    if(option){
        doSome();
    }
})

option_page:

<html>
    <head>
        <title>My Test Extension Options</title>
    </head>
    <body>
        option: <input id="option" type="text" /><br />
        <input id="save" type="submit" /><br />
        <span id="tips">option saved</span>
        <script type="text/javascript">
            (function(){
                var input=document.getElementById('option');
                var save=document.getElementById('save');
                var tips=document.getElementById('tips');
                input.value=localStorage.option||'';
            // Here localStorage.option is what I want content_scripts to get.
                function hideTips(){
                    tips.style.visibility='hidden';
                }
                function saveHandler(){
                    localStorage.option=input.value||'';
                    tips.style.visibility='visible';
                    setTimeout(hideTips,1000);
                }
                hideTips();
                save.addEventListener('click',saveHandler);
            })();
        </script>
    </body>
</html>
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would think you could use the chrome.extensions.* API to create a line of communication to a background page that is running under your extension ID, thus giving you local storage.

    I think this is possible because the Content Script docs specify that the chrome.extensions* API’s are available to content scripts. But I have never tried this.

    You would then just have to send messages from the background page to the content script when a connection is made. You could even send one message with all the settings in a literal object.

    Here is an example of creating two way communication I wrote about earlier. You could implement this or create a custom solution but I think this is how you would achieve what you are looking for.

    • 0