Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: [INFOREQ][3.0.0] IE bug in EditorGridPanel with DateField when using ext-lang-fr.js

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #11

    Default

    Can you just try something else ??? Just remove some line in ext-base.js, override function :

    Code:
     override: function(origclass, overrides){
      if(overrides){
       var p = origclass.prototype;
       for(var method in overrides){
        p[method] = overrides[method]
       }
       if(/*Ext.isIE &&*/ overrides.toString != origclass.toString){
        p.toString = overrides.toString
       }
      }
     }
    putting that in comment makes ALL my browsers act the same way!!!

    Also tried on a different machine with IE 8... and others, all browsers, all machines by putting this in comment! Now if you can't reproduce that BUG, I don't know why... maybe my french versions on WinXP???

  2. #12

    Default

    Ok, here's an example reproducing this BUG on any machine, any browsers, any Ext version that i've tried... thank you!

    Code:
    <html>
    <head>
     <link rel="stylesheet" type="text/css" href="../../resources/css/ext-all.css">
     <script type="text/javascript" src="../../adapter/ext/ext-base.js"></script>
     <script type="text/javascript" src="../../ext-all.js"></script>
    </head>
    <body>
    <script type="text/javascript">
    Ext.apply(Ext, {
     override: function(origclass, overrides){
      if(overrides){
       var p = origclass.prototype;
       Ext.apply(p, overrides);
       if(/*Ext.isIE && */overrides.toString != origclass.toString){
        p.toString = overrides.toString;
       }
      }
     }
    });
    Date.parseCodes.S.s = "(?:er)";
    Ext.override(Date, {
     getSuffix: function() {
      return (this.getDate() == 1) ? "er" : "";
     }
    });
    Ext.onReady(function(){
     var cm = new Ext.grid.ColumnModel([
      {
       header: 'ID',
       dataIndex: 'id'
      },{
       header: 'Display',
       dataIndex: 'display',
       renderer: function(value){
        return(value ? value.dateFormat('Y-m-d') : '');
       },
       editor: new Ext.form.DateField({
        format: 'Y-m-d'
       })
      }
     ]);
     new Ext.grid.EditorGridPanel({
      width: 300,
      height: 200,
      renderTo: Ext.getBody(),
      title: "Editor Grid example bug",
      store: new Ext.data.JsonStore({
       fields: [
        {type: 'int', name: 'id'},
        {type: 'date', name: 'display', dateFormat: 'Y-m-d'}
       ],
       data: [
        {id: '1', display: '2009-01-01'},
        {id: '2', display: '2009-01-02'},
        {id: '3', display: '2009-01-03'}
       ]
      }),
      cm: cm
     });
    });
    </script>
    </body>
    </html>

  3. #13
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246

    Default

    This has already been fixed somewhere between Ext 3.0.0 and 3.0.3, because Ext.override now is defined as:
    Code:
    Ext.override = function(origclass, overrides){
        if(overrides){
            var p = origclass.prototype;
            Ext.apply(p, overrides);
            if(Ext.isIE && overrides.hasOwnProperty('toString')){
                p.toString = overrides.toString;
            }
        }
    }

  4. #14

    Default

    Ok, it worked, but in my 3.0.3 here, it still like the old method!

  5. #15
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246

    Default

    Quote Originally Posted by ylaroche View Post
    Ok, it worked, but in my 3.0.3 here, it still like the old method!
    I just checked: This was changed in Ext 3.0.2, so both Ext 3.0.2 and 3.0.3 contain the code I listed.

    Are you sure you are working with Ext 3.0.3?

  6. #16

    Default

    Yep... Public release, i've just downloaded few seconds ago just to check, and it still like the old method!

  7. #17
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246

    Default

    You are correct. The core files in SVN are not correctly branched for the Ext 3.0.x subreleases, so in every release I checked I was always looking at the most current core files.

    That means that this change will be part of Ext 3.0.4 and 3.1.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •