Musachy Barroso wrote:
...
Okay, that makes more sense for the case where separateScripts is false,
but now I'm having second thoughts about my interpretation of
executeScripts and WW-2501.
bind and contentPane do this:
if (this.executeScripts) {
var parsed= this.parse(data)
this.setContent(parsed.text)
this._executeScipts(parsed.scripts)
} else {
this.setContent(data);
}
So, executeScripts must be true for separation to occur or not
(excecuteScripts takes precendence, not how I interpreted it).
Delving into the _executeScripts function, in pseudo code:
var code = concatenateScripts();
if (this.scriptSeparation) {
create Function containing code and invoke it
} else {
if the execScript() method exists, invoke it to execute the code;
else create a script node, add the code to it and add the script node
to the DOM
}
This latter section seems to be the source of user problems. The
execScript method is IE specific, hence the detection of that first.
If it's not present, the code relies on the browser executing the
scripts after the node is added.
(I didn't think FF did this...I have to check)
The suggested fix for WW-2501 bypassed the execScript() method detection
and doesn't help at all.
Have a missed something in this interpretation Musachy?
I suspect most users problems are therefore that:
- their inline code can't be concatenated (eg. missing a semicolon or
variable namespace clashes)
- their inline code assumes the DOM is in a state it isn't (eg. waiting
for an event or existence of an object)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
