Artur Bodera (Joust)
30 Apr 2009, 6:05 AM
Since Ext 1.1.1 the Ext.DomHelper.useDom=true has been dumped (?). Nothing in the source code for Ext Core either.
Problem is, the following will not work in IE6/IE7:
Ext.get('mySelectElement').createChild({
tag:'option',
value:'some value',
html:'New option for select'
});
Same goes for insertBefore, append, insertHtml, overwrite and other methods. That is because IE has a bug with several form elements and innerHTML, which DomHelper heavily relies on!
This is confirmed by Microsoft: http://support.microsoft.com/kb/276228 (http://support.microsoft.com/kb/276228)
There is a discusion about innerHTML and useDom in ext 1.1.1: http://www.extjs.com/forum/showthread.php?t=13409&highlight=innerHTML+select+explorer
Here is a solution: http://domscripting.com/blog/display/99
Implementation in ext would be fairly simple - use the following workaround when Ext.isIE7 || Ext.isE6 (haven't tested under IE8 yet) and el.parent('form')
With best regards.
Artur Bodera
Problem is, the following will not work in IE6/IE7:
Ext.get('mySelectElement').createChild({
tag:'option',
value:'some value',
html:'New option for select'
});
Same goes for insertBefore, append, insertHtml, overwrite and other methods. That is because IE has a bug with several form elements and innerHTML, which DomHelper heavily relies on!
This is confirmed by Microsoft: http://support.microsoft.com/kb/276228 (http://support.microsoft.com/kb/276228)
There is a discusion about innerHTML and useDom in ext 1.1.1: http://www.extjs.com/forum/showthread.php?t=13409&highlight=innerHTML+select+explorer
Here is a solution: http://domscripting.com/blog/display/99
Implementation in ext would be fairly simple - use the following workaround when Ext.isIE7 || Ext.isE6 (haven't tested under IE8 yet) and el.parent('form')
With best regards.
Artur Bodera