'ActiveXObject' is not defined no-undef [React-Js]












1















I am trying to parse XML Response un ReactJs.



var parser, xmlDoc;
var text = "<bookstore><book>" +
"<title>Everyday Italian</title>" +
"<author>Giada De Laurentiis</author>" +
"<year>2005</year>" +
"</book></bookstore>";

if (window.DOMParser) {
// code for modern browsers
parser = new DOMParser();
xmlDoc = parser.parseFromString(text,"text/xml");
} else {
// code for old IE browsers
xmlDoc = new ActiveXObject("Microsoft.XMLDOM");
xmlDoc.async = false;
xmlDoc.loadXML(text);
}


Above code works fine in React if i remove else part , but project requirement is to support >=IE7 browsers using ReactJs. Also above code is working good if i embed JS into simple HTML page. Please let me know if i am missing something.










share|improve this question























  • So define it as a global on the page.

    – epascarello
    Nov 21 '18 at 13:23











  • Not the complete answer you're looking for since I'm not familiar with old browser support but you should make your else an else if and also check for the existence of ActiveXObject (like you did with DOMParser) before using it. This will at least get rid of your error.

    – Vgoose
    Nov 21 '18 at 13:24


















1















I am trying to parse XML Response un ReactJs.



var parser, xmlDoc;
var text = "<bookstore><book>" +
"<title>Everyday Italian</title>" +
"<author>Giada De Laurentiis</author>" +
"<year>2005</year>" +
"</book></bookstore>";

if (window.DOMParser) {
// code for modern browsers
parser = new DOMParser();
xmlDoc = parser.parseFromString(text,"text/xml");
} else {
// code for old IE browsers
xmlDoc = new ActiveXObject("Microsoft.XMLDOM");
xmlDoc.async = false;
xmlDoc.loadXML(text);
}


Above code works fine in React if i remove else part , but project requirement is to support >=IE7 browsers using ReactJs. Also above code is working good if i embed JS into simple HTML page. Please let me know if i am missing something.










share|improve this question























  • So define it as a global on the page.

    – epascarello
    Nov 21 '18 at 13:23











  • Not the complete answer you're looking for since I'm not familiar with old browser support but you should make your else an else if and also check for the existence of ActiveXObject (like you did with DOMParser) before using it. This will at least get rid of your error.

    – Vgoose
    Nov 21 '18 at 13:24
















1












1








1








I am trying to parse XML Response un ReactJs.



var parser, xmlDoc;
var text = "<bookstore><book>" +
"<title>Everyday Italian</title>" +
"<author>Giada De Laurentiis</author>" +
"<year>2005</year>" +
"</book></bookstore>";

if (window.DOMParser) {
// code for modern browsers
parser = new DOMParser();
xmlDoc = parser.parseFromString(text,"text/xml");
} else {
// code for old IE browsers
xmlDoc = new ActiveXObject("Microsoft.XMLDOM");
xmlDoc.async = false;
xmlDoc.loadXML(text);
}


Above code works fine in React if i remove else part , but project requirement is to support >=IE7 browsers using ReactJs. Also above code is working good if i embed JS into simple HTML page. Please let me know if i am missing something.










share|improve this question














I am trying to parse XML Response un ReactJs.



var parser, xmlDoc;
var text = "<bookstore><book>" +
"<title>Everyday Italian</title>" +
"<author>Giada De Laurentiis</author>" +
"<year>2005</year>" +
"</book></bookstore>";

if (window.DOMParser) {
// code for modern browsers
parser = new DOMParser();
xmlDoc = parser.parseFromString(text,"text/xml");
} else {
// code for old IE browsers
xmlDoc = new ActiveXObject("Microsoft.XMLDOM");
xmlDoc.async = false;
xmlDoc.loadXML(text);
}


Above code works fine in React if i remove else part , but project requirement is to support >=IE7 browsers using ReactJs. Also above code is working good if i embed JS into simple HTML page. Please let me know if i am missing something.







javascript reactjs activexobject






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 13:18









Yash ChauhanYash Chauhan

83




83













  • So define it as a global on the page.

    – epascarello
    Nov 21 '18 at 13:23











  • Not the complete answer you're looking for since I'm not familiar with old browser support but you should make your else an else if and also check for the existence of ActiveXObject (like you did with DOMParser) before using it. This will at least get rid of your error.

    – Vgoose
    Nov 21 '18 at 13:24





















  • So define it as a global on the page.

    – epascarello
    Nov 21 '18 at 13:23











  • Not the complete answer you're looking for since I'm not familiar with old browser support but you should make your else an else if and also check for the existence of ActiveXObject (like you did with DOMParser) before using it. This will at least get rid of your error.

    – Vgoose
    Nov 21 '18 at 13:24



















So define it as a global on the page.

– epascarello
Nov 21 '18 at 13:23





So define it as a global on the page.

– epascarello
Nov 21 '18 at 13:23













Not the complete answer you're looking for since I'm not familiar with old browser support but you should make your else an else if and also check for the existence of ActiveXObject (like you did with DOMParser) before using it. This will at least get rid of your error.

– Vgoose
Nov 21 '18 at 13:24







Not the complete answer you're looking for since I'm not familiar with old browser support but you should make your else an else if and also check for the existence of ActiveXObject (like you did with DOMParser) before using it. This will at least get rid of your error.

– Vgoose
Nov 21 '18 at 13:24














1 Answer
1






active

oldest

votes


















1














So use window.ActiveXObject instead of just ActiveXObject to get around the global. I assume your linter is set up to allow window.



or set up your linter to allow it



"eslintConfig": {
"globals": {
"window": true,
"ActiveXObject": true
}
}


or set it on the page



/* global ActiveXObject */





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%2f53412949%2factivexobject-is-not-defined-no-undef-react-js%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









    1














    So use window.ActiveXObject instead of just ActiveXObject to get around the global. I assume your linter is set up to allow window.



    or set up your linter to allow it



    "eslintConfig": {
    "globals": {
    "window": true,
    "ActiveXObject": true
    }
    }


    or set it on the page



    /* global ActiveXObject */





    share|improve this answer




























      1














      So use window.ActiveXObject instead of just ActiveXObject to get around the global. I assume your linter is set up to allow window.



      or set up your linter to allow it



      "eslintConfig": {
      "globals": {
      "window": true,
      "ActiveXObject": true
      }
      }


      or set it on the page



      /* global ActiveXObject */





      share|improve this answer


























        1












        1








        1







        So use window.ActiveXObject instead of just ActiveXObject to get around the global. I assume your linter is set up to allow window.



        or set up your linter to allow it



        "eslintConfig": {
        "globals": {
        "window": true,
        "ActiveXObject": true
        }
        }


        or set it on the page



        /* global ActiveXObject */





        share|improve this answer













        So use window.ActiveXObject instead of just ActiveXObject to get around the global. I assume your linter is set up to allow window.



        or set up your linter to allow it



        "eslintConfig": {
        "globals": {
        "window": true,
        "ActiveXObject": true
        }
        }


        or set it on the page



        /* global ActiveXObject */






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 13:27









        epascarelloepascarello

        154k14136185




        154k14136185
































            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%2f53412949%2factivexobject-is-not-defined-no-undef-react-js%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

            How to change which sound is reproduced for terminal bell?

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents