addEventListener execute JSX only the first time

Question

as the subject suggests while testing some listeners I found this strange behavior: the addEventListener does get triggered, the callback get called but the evalScript invoking the JSX runs only the first time.

This is how I'm doing it:

ext.JS

function doSomething(){
 document.getElementById("placeholder").innerHTML += "+";
 csInterface.evalScript("JSXdoSomething",
    function(result){
        document.getElementById("docName").innerHTML += result + ", ";
    });
}

var csInterface = new CSInterface();
csInterface.addEventListener("documentAfterActivate",doSomething);

in the JSX I have:

JSXdoSomething = pleaseDo()
function pleaseDo(){
    return app.activeDocument.name;
}  

now, when switching between documents, this line get executed every time:

document.getElementById("placeholder").innerHTML += "+";  

but the evalScript works only the first time.

PSA: if you already have a document opened and you open the extension documentAfterActivate gets fired.

E.g.:
we have 2 documents open: Doc1 and Doc2, the output I'm getting while switching between the two: "placeholder" = ++++++...
"docName" = Doc1, Doc1, Doc1, Doc1...

I've also tried to call the evalScript in this way:
a) csInterface.evalScript("pleaseDo" ...
or
b) csInterface.evalScript("pleaseDo()" ...

for a) I get the same behavior as described above and for b) I get "EvalScript Error."

I tried to change the JSX in this way:

$._doSomething = function(){
   return app.activeDocument.name;
}  

and call it like this:
csInterface.evalScript("$._doSomething" ...

I get the same behavior as before: the evalScript get executed only the first time and for the subsequent times the value stored in the return is always the name of the first Document.
I've also tried to put an alert in the JSX function and sure enough I don't get the pop-up every time I change the document but only the first time.

Have you played with the events? Can you point me in the right direction?

Answer 1

Use innerText instead of innerHTML

You should avoid using innerHTML in almost all cases, because it basically creates an entirely new element. It is much better to set styles, attributes, or text changes directly on the existing element