Custom Values in Manifest.json for Chrome Extensions?












6















Is it allowed to have custom values saved in manifest.json for a Chrome extension?
Because it is json, I want to save some information in manifest.json, especially because Chrome API is available for Opera, I need some distinguish data.



Does Chrome store complain if there is any custom data in manifest.json?










share|improve this question























  • Is there a reason you need to put it in the manifest instead of another json file?

    – Daniel Herr
    Mar 11 '16 at 21:11











  • There is non-standard data available for Opera and other Chrome API compatible browsers. So rather than creating different files, I thought to keep distinguish data in manifest.json so that I can have global source code that may work for all browsers.

    – John Sewell
    Mar 11 '16 at 22:33
















6















Is it allowed to have custom values saved in manifest.json for a Chrome extension?
Because it is json, I want to save some information in manifest.json, especially because Chrome API is available for Opera, I need some distinguish data.



Does Chrome store complain if there is any custom data in manifest.json?










share|improve this question























  • Is there a reason you need to put it in the manifest instead of another json file?

    – Daniel Herr
    Mar 11 '16 at 21:11











  • There is non-standard data available for Opera and other Chrome API compatible browsers. So rather than creating different files, I thought to keep distinguish data in manifest.json so that I can have global source code that may work for all browsers.

    – John Sewell
    Mar 11 '16 at 22:33














6












6








6


1






Is it allowed to have custom values saved in manifest.json for a Chrome extension?
Because it is json, I want to save some information in manifest.json, especially because Chrome API is available for Opera, I need some distinguish data.



Does Chrome store complain if there is any custom data in manifest.json?










share|improve this question














Is it allowed to have custom values saved in manifest.json for a Chrome extension?
Because it is json, I want to save some information in manifest.json, especially because Chrome API is available for Opera, I need some distinguish data.



Does Chrome store complain if there is any custom data in manifest.json?







javascript json google-chrome google-chrome-extension chrome-web-store






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 11 '16 at 10:56









John SewellJohn Sewell

389113




389113













  • Is there a reason you need to put it in the manifest instead of another json file?

    – Daniel Herr
    Mar 11 '16 at 21:11











  • There is non-standard data available for Opera and other Chrome API compatible browsers. So rather than creating different files, I thought to keep distinguish data in manifest.json so that I can have global source code that may work for all browsers.

    – John Sewell
    Mar 11 '16 at 22:33



















  • Is there a reason you need to put it in the manifest instead of another json file?

    – Daniel Herr
    Mar 11 '16 at 21:11











  • There is non-standard data available for Opera and other Chrome API compatible browsers. So rather than creating different files, I thought to keep distinguish data in manifest.json so that I can have global source code that may work for all browsers.

    – John Sewell
    Mar 11 '16 at 22:33

















Is there a reason you need to put it in the manifest instead of another json file?

– Daniel Herr
Mar 11 '16 at 21:11





Is there a reason you need to put it in the manifest instead of another json file?

– Daniel Herr
Mar 11 '16 at 21:11













There is non-standard data available for Opera and other Chrome API compatible browsers. So rather than creating different files, I thought to keep distinguish data in manifest.json so that I can have global source code that may work for all browsers.

– John Sewell
Mar 11 '16 at 22:33





There is non-standard data available for Opera and other Chrome API compatible browsers. So rather than creating different files, I thought to keep distinguish data in manifest.json so that I can have global source code that may work for all browsers.

– John Sewell
Mar 11 '16 at 22:33












1 Answer
1






active

oldest

votes


















0














No, it's not allowed to use custom values in Chrome Extension manifest.json file. You can refer below given link. @John



https://developer.chrome.com/extensions/manifest


You can only use those parameters in manifest.json. If you will use others parameters rather than allowed, it will throw an error at time of importing chrome extension.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f35938426%2fcustom-values-in-manifest-json-for-chrome-extensions%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    No, it's not allowed to use custom values in Chrome Extension manifest.json file. You can refer below given link. @John



    https://developer.chrome.com/extensions/manifest


    You can only use those parameters in manifest.json. If you will use others parameters rather than allowed, it will throw an error at time of importing chrome extension.






    share|improve this answer




























      0














      No, it's not allowed to use custom values in Chrome Extension manifest.json file. You can refer below given link. @John



      https://developer.chrome.com/extensions/manifest


      You can only use those parameters in manifest.json. If you will use others parameters rather than allowed, it will throw an error at time of importing chrome extension.






      share|improve this answer


























        0












        0








        0







        No, it's not allowed to use custom values in Chrome Extension manifest.json file. You can refer below given link. @John



        https://developer.chrome.com/extensions/manifest


        You can only use those parameters in manifest.json. If you will use others parameters rather than allowed, it will throw an error at time of importing chrome extension.






        share|improve this answer













        No, it's not allowed to use custom values in Chrome Extension manifest.json file. You can refer below given link. @John



        https://developer.chrome.com/extensions/manifest


        You can only use those parameters in manifest.json. If you will use others parameters rather than allowed, it will throw an error at time of importing chrome extension.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 24 '18 at 13:22









        Ghanshyam KatriyaGhanshyam Katriya

        649725




        649725
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f35938426%2fcustom-values-in-manifest-json-for-chrome-extensions%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            TypeError: fit_transform() missing 1 required positional argument: 'X'