Threaded View
-
8 Apr 2009 8:27 PM #1
[FIXED?] [3.0] TriggerField / r2213 and IE8
[FIXED?] [3.0] TriggerField / r2213 and IE8
Jack put in r2213 before IE8 was out to deal with some IE problems apparently. However, in IE8 it messes up twin trigger fields that I have created. Perhaps it should be limited to IE6 and IE7. Which works for me. Thanks!
In addition: the CSS fixes for the ie bogus margin bug should be restricted to IE6 and IE7 in form.css:Code:afterRender : function(){ Ext.form.TriggerField.superclass.afterRender.call(this); var y; if((Ext.isIE6||Ext.isIE7) && !this.hideTrigger && this.el.getY() != (y = this.trigger.getY())){ this.el.position(); this.el.setY(y); } }
Code:.ext-ie6 .x-small-editor .x-form-text,.ext-ie7 .x-small-editor .x-form-text { margin-top:-1px !important; /* ie bogus margin bug */ margin-bottom:-1px !important; height:20px !important; /* ie quirks */ line-height:16px !important; }Code:.ext-ie6 .x-form-text,.ext-ie7 .x-form-text { margin:-1px 0; /* ie bogus margin bug */ height:22px; /* ie quirks */ line-height:18px; }Code:.ext-ie6 textarea.x-form-field,.ext-ie7 textarea.x-form-field { margin:-1px 0; /* ie bogus margin bug */ }Last edited by stever; 14 Apr 2009 at 8:30 PM. Reason: Fix for CSS added
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote