contractor
29 Nov 2007, 7:13 AM
[1.1] & [1.1.1]
I am implementing DIV-based "popups". These are successfully working in Firefox and I can display a page with multiple links that successfully pop up my DIV windows as many as I want on a page.
STARTED TEST USING EXT 1.1
On IE (tried Internet Explorer 6 & 7, no other IE version tried yet) I can pop up only one DIV and then I get an "invalid argument" error. My debugger highlights the following javascript code as the culprit:
this.dom.style[_91]=_90;
which is in code taken from line 20 of ext-core.js. FYI here is a fuller snapshot of this culprit:
....{if(typeof _8f=="string"){var _91;if(!(_91=_4[_8f])){_91=_4[_8f]=_8f.replace(_5,_6);}if(_91=="opacity"){this.setOpacity(_90);}else{this.dom.style[_91]=_90;}}...
The debugger shows that the following values are in place at the time of the exception:
_91 = "width"
_90 = NaN ( _90 shows up as a Double )
I THEN UPGRADED TO EXT 1.1.1
Now I get a similar "invalid argument" error in the the same general EXT code area (some variable names changed from 1.1 to 1.1.1) as shown below:
[CODE] ...if(camel=="opacity"){this.setOpacity(value)}else{this.dom.style[camel]=value}}else... [\CODE]
The actual culprit from the above code line is "...{this.dom.style[camel]=value}..."
Similar to 1.1 values, my debugger now shows the following values for the 1.1.1 code:
camel = "width"
value = NaN
Anyone have a workaround for IE?
I am implementing DIV-based "popups". These are successfully working in Firefox and I can display a page with multiple links that successfully pop up my DIV windows as many as I want on a page.
STARTED TEST USING EXT 1.1
On IE (tried Internet Explorer 6 & 7, no other IE version tried yet) I can pop up only one DIV and then I get an "invalid argument" error. My debugger highlights the following javascript code as the culprit:
this.dom.style[_91]=_90;
which is in code taken from line 20 of ext-core.js. FYI here is a fuller snapshot of this culprit:
....{if(typeof _8f=="string"){var _91;if(!(_91=_4[_8f])){_91=_4[_8f]=_8f.replace(_5,_6);}if(_91=="opacity"){this.setOpacity(_90);}else{this.dom.style[_91]=_90;}}...
The debugger shows that the following values are in place at the time of the exception:
_91 = "width"
_90 = NaN ( _90 shows up as a Double )
I THEN UPGRADED TO EXT 1.1.1
Now I get a similar "invalid argument" error in the the same general EXT code area (some variable names changed from 1.1 to 1.1.1) as shown below:
[CODE] ...if(camel=="opacity"){this.setOpacity(value)}else{this.dom.style[camel]=value}}else... [\CODE]
The actual culprit from the above code line is "...{this.dom.style[camel]=value}..."
Similar to 1.1 values, my debugger now shows the following values for the 1.1.1 code:
camel = "width"
value = NaN
Anyone have a workaround for IE?