I have further isolated it to this bit of code inside Element:
var hasCloneBug = (function(test){
test.innerHTML = '<object><param name="should_fix" value="the
unknown"></object>';
return test.cloneNode(true).firstChild.childNodes.length != 1;
})(document.createElement('div'));
When that is present the error appears in the browser. Is this a critical
piece of code? Is there an alternative? Its nested inside of a <ltIE9>
block which makes me think its there for IE8...
Thanks,
Michael
On Tuesday, August 26, 2014 9:17:25 AM UTC-6, Michael wrote:
>
> I have isolated an IE 9 issue we are encountering to MooTools Core 1.5.0.
> It did not happen before the upgrade, and only happens on some of our
> browsers.
>
> Env:
> - Windows Server 2008 R2 Standard SP1
> - Internet Explorer 9.0.8112.16421 (Update Versions 9.0.21)
>
> Repro:
> - load page that has mootools core.js included in the header.
>
> I have methodically isolated the bug to the in the Element chunk of
> mootools code. I haven't dug into exactly what yet, but wanted to check if
> this is a known issue and/or if a fix already exists.
>
> Thanks in advance,
> Michael
>
--
---
You received this message because you are subscribed to the Google Groups
"MooTools Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
