Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Ext JS Premium Member stever's Avatar
    Join Date
    Mar 2007
    Posts
    1,407
    Vote Rating
    6
    stever will become famous soon enough stever will become famous soon enough

      0  

    Default [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!

    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);
            }
        }
    In addition: the CSS fixes for the ie bogus margin bug should be restricted to IE6 and IE7 in form.css:

    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

  2. #2
    Ext JS Premium Member stever's Avatar
    Join Date
    Mar 2007
    Posts
    1,407
    Vote Rating
    6
    stever will become famous soon enough stever will become famous soon enough

      0  

    Default


    Someone ought to take a look at these IE specific css rules and see which are needed for IE8 and which are not. I stumbed across that when I accidentally took out the ext-ie class from the body and everything that was off suddenly looked good! Not a thorough test, of course but did get me looking at the ext-ie CSS code...

  3. #3
    Sencha - Ext JS Dev Team evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    16,953
    Vote Rating
    636
    evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute

      0  

    Default


    I'm checking out the form related stuff in IE8 now. Once the margin bug is fixed for text fields, it looks mostly ok.
    Evan Trimboli
    Sencha Developer
    Twitter - @evantrimboli
    Don't be afraid of the source code!

  4. #4
    Ext JS Premium Member stever's Avatar
    Join Date
    Mar 2007
    Posts
    1,407
    Vote Rating
    6
    stever will become famous soon enough stever will become famous soon enough

      0  

    Default


    This is marked as fixed, but the afterRender function is still IE version indiscriminate. Which might be on purpose, just don't think it is...

Thread Participants: 1