Sencha Forum - Ext 3.x: Bugs http://www.sencha.com/forum/ Report bugs in Ext JS version 3.x en Thu, 23 May 2013 19:21:21 GMT vBulletin 60 http://www.sencha.com/forum/images/misc/rss.png Sencha Forum - Ext 3.x: Bugs http://www.sencha.com/forum/ <![CDATA[[OPEN] Ext JS 3.4.1.1 - CSS class 'ext-gecko' is absent on BODY under Gecko-based browsers]]> http://www.sencha.com/forum/showthread.php?262960-Ext-JS-3.4.1.1-CSS-class-ext-gecko-is-absent-on-BODY-under-Gecko-based-browsers&goto=newpost Mon, 06 May 2013 08:10:33 GMT *_Ext version tested:_* * Ext 3.4.1.1 *_Browser versions tested against:_* * Any Gecko-based browsers (e.g. FF17) *_Description:_* ... Ext version tested:
  • Ext 3.4.1.1
Browser versions tested against:
  • Any Gecko-based browsers (e.g. FF17)
Description:
  • CSS class 'ext-gecko' is absent on BODY under Gecko-based browsers
Steps to reproduce the problem: The result that was expected: Possible fix:

http://cdn.sencha.com/ext/gpl/3.4.1....ventManager.js (line 646)
Code:
        if (Ext.isGecko) {
            cls.push('ext-gecko');
            if (Ext.isGecko2) {
                cls.push('ext-gecko2');
            } else {
                cls.push('ext-gecko3');
            }
        }
or
Code:
Ext.onReady(function () {
    if (Ext.isGecko) {
        Ext.getBody().addClass('ext-gecko');
    }
});
]]> Ext 3.x: Bugs asinko http://www.sencha.com/forum/showthread.php?262960-Ext-JS-3.4.1.1-CSS-class-ext-gecko-is-absent-on-BODY-under-Gecko-based-browsers <![CDATA[[OPEN] 3.4.1.1 Ext.define() breaks the xtype reference]]> http://www.sencha.com/forum/showthread.php?262945-3.4.1.1-Ext.define()-breaks-the-xtype-reference&goto=newpost Mon, 06 May 2013 04:04:29 GMT _*REQUIRED INFORMATION*_ *_Ext version tested:_* * Ext 3.4.1.1 *_Browser versions tested against:_* * Chrome 26 * FF 20 REQUIRED INFORMATION


Ext version tested:
  • Ext 3.4.1.1
Browser versions tested against:
  • Chrome 26
  • FF 20
Description:
  • Ext.define() breaks the xtype reference. Instances of components extended through Ext.define() end up having the wrong constructor.
Steps to reproduce the problem:
  • Define and extend an Ext component.
  • Specify an xtype.
  • Create an instance of the newly defined component.
  • Call getXType() on the new component instance.
The result that was expected:
  • the returned xtype should reflect the one defined for the new component.
The result that occurs instead:
  • the returned xtype does not reflect the one defined for the new component, but its parent.
Test Case:

Code:
// Classic way
Ext.ns('Test.CustomPanel');
Test.CustomPanel = Ext.extend(Ext.Panel, {
  xtype: 'custompanel'
});
Ext.reg('custompanel', Test.CustomPanel);

var c = Ext.create({ xtype: 'custompanel' });

c.getXType()
"custompanel"  // CORRECT


c.getXTypes()
"component/box/container/panel/custompanel"  // CORRECT
Code:
// With Ext.define()Ext.define('Test.CustomPanel', {
  extend: 'Ext.Panel',
  xtype: 'custompanel'
});

var c = Ext.create({ xtype: 'custompanel' });

c.getXType()
"panel"  // INCORRECT

c.getXTypes()
"component/box/container/panel"  // INCORRECT
HELPFUL INFORMATION


Debugging already done:
  • Instances of components extended through Ext.define() end up having the wrong constructor.
Possible fix:
  • not provided
Operating System:
  • MAC OSX
]]> Ext 3.x: Bugs SimoAmi http://www.sencha.com/forum/showthread.php?262945-3.4.1.1-Ext.define()-breaks-the-xtype-reference <![CDATA[[OPEN] Fileupload textfield will not render to correct width in non active tabpanel]]> http://www.sencha.com/forum/showthread.php?262727-Fileupload-textfield-will-not-render-to-correct-width-in-non-active-tabpanel&goto=newpost Thu, 02 May 2013 08:16:28 GMT I found this a little weird behavior. The textfield where the filename will be shown will not render to the correct width in the 2nd tab. Now, if i... I found this a little weird behavior.
The textfield where the filename will be shown will not render to the correct width in the 2nd tab.
Now, if i change deferredRender from FALSE to TRUE, it now renders properly when I select the 2nd tab.
But I need to render and populate the other textfields in advance for other information.(I cleaned up the code and removed the other fields just to shorten the code )

How to fix this? Is this a known bug?

Code:
var form2 = new Ext.FormPanel({
        url:'../whatever.php',
        method: 'POST',
        fileUpload: true,
        items: [ {
                xtype:'tabpanel',
                activeItem: 0,
                border: false,
                anchor: '100% 100%',

                deferredRender: false,

                items: [{
                    title: 'tab1',
                    items: [ {
                        xtype: 'fileuploadfield',
                        id: 'form-file',
                        emptyText: 'Select an image',
                        fieldLabel: 'Item Photo',
                        allowBlank: true,
                        name: 'image',
                        buttonText: '',
                        width: 200,
                        buttonCfg: {
                            iconCls: 'upload-icon'
                        }
                    }]
                }, {
                    title: 'tab2',
                    items: [ {
                        xtype: 'fileuploadfield',
                        id: 'form2-file',
                        emptyText: 'Select an image',
                        fieldLabel: 'Item Photo',
                        allowBlank: true,
                        name: 'image',
                        buttonText: '',
                        width: 200,
                        buttonCfg: {
                            iconCls: 'upload-icon'
                        }
                    }]
                }]
        }]
    });
var win = new Ext.Window({
        iconCls: 'edit',
        title: "test",
        layout: 'fit',
        width: 700,
        height: 600,
        closeAction: 'close',
        modal: true,
        resizable: false,
        frame: true,
        plain: true,
        items: form2,
        buttons: [{
            text:'Update',
            handler: function() {               

            }
        }, {
            text: 'Reset',
            handler: function(){

            }
        }, {
            text: 'Cancel',
            handler: function(){
                win.close();
            }
        }]
    });
    win.show();
]]> Ext 3.x: Bugs Chaoz http://www.sencha.com/forum/showthread.php?262727-Fileupload-textfield-will-not-render-to-correct-width-in-non-active-tabpanel <![CDATA[[OPEN] removal of activeX 'Msxml2.XMLHTTP.6.0' in 3.4.1.1 - why?]]> http://www.sencha.com/forum/showthread.php?262701-removal-of-activeX-Msxml2.XMLHTTP.6.0-in-3.4.1.1-why&goto=newpost Wed, 01 May 2013 20:55:16 GMT In ext-base-debug.js beginning at line 2186 the following change was made. Is this correct? Can someone explain why this was done? 3.4.1 ... In ext-base-debug.js beginning at line 2186 the following change was made. Is this correct? Can someone explain why this was done?

3.4.1
Code:
Ext.lib.Ajax = function() {
    var activeX = ['Msxml2.XMLHTTP.6.0',
                  'Msxml2.XMLHTTP.3.0',
                  'Msxml2.XMLHTTP'],
3.4.1.1
Code:
Ext.lib.Ajax = function() {
    var activeX = ['Msxml2.XMLHTTP.3.0',
                  'Msxml2.XMLHTTP'],
Thanks. ]]> Ext 3.x: Bugs rich02818 http://www.sencha.com/forum/showthread.php?262701-removal-of-activeX-Msxml2.XMLHTTP.6.0-in-3.4.1.1-why <![CDATA[[INFOREQ] A bug in Ext.grid.PivotAxis]]> http://www.sencha.com/forum/showthread.php?262138-A-bug-in-Ext.grid.PivotAxis&goto=newpost Wed, 24 Apr 2013 05:32:11 GMT I found a bug in the method buildHeaders of Ext.grid.PivotAxis. Look at the following code snapshot:


/* * 'changed' indicates that we need to create a new cell. This should be true whenever the cell * above (previousHeader) is different from this cell, or when the cell on the previous dimension * changed (e.g. if the current dimension is Product and the previous was Person, we need to start * a new cell if Product is the same but Person changed, so we check the previous dimension and tuple) */ changed = previousHeader != undefined && previousHeader != currentHeader; if (i > 0 && j > 0) { changed = changed || tuple.data[dimensions[i-1].dataIndex] != tuples[j-1].data[dimensions[i-1].dataIndex]; }
I think it is not enough just to check previous dimension. Instead all the preceding dimensions should be compared. So my fix is like below:

isPrecedingChanged : function(tuples,dimensions,currentCol,currentRow){
var changed = false;
for(var col= currentCol; col>0; col--){
if(tuples[currentRow].data[dimensions[col-1].dataIndex]!=tuples[currentRow-1].data[dimensions[col-1].dataIndex]){
changed = true;
break;
}
}
return changed;
},
…..
changed = previousHeader !== undefined && previousHeader != currentHeader;
if (i > 0 && j > 0) {
changed = changed || me.isPrecedingChanged(tuples,dimensions,i,j);
}
….. ]]> Ext 3.x: Bugs wuxi7227 http://www.sencha.com/forum/showthread.php?262138-A-bug-in-Ext.grid.PivotAxis