Results 1 to 5 of 5

Thread: [4.1 B2] Trigger/Combo separated from fieldbody on Windows webserver

    Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. #1
    Sencha - Documentation Team slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,162
    Vote Rating
    257
      0  

    Default [4.1 B2] Trigger/Combo separated from fieldbody on Windows webserver

    REQUIRED INFORMATION Ext version tested:
    • Ext 4.1 rev B2

    Browser versions tested against:
    • IE8
    • FF5 (firebug 1.8.1)

    DOCTYPE tested against:
    • strict

    Description:
    • Trigger/combo fields have their triggers separated from the field body in IE8 on 4.1 B2 when run from a Windows 2008R2 webserver. Same sample script works ok on the same server in 4.0.7, works in IE8 from the file system, and works ok on FF5.

    Steps to reproduce the problem:
    • Just need a trigger or combobox.

    The result that was expected:
    • Trigger should be married to the field body.

    The result that occurs instead:
    • The trigger is separated from the field body when the script is run on a Windows 2008R2 webserver.

    Test Case:
    Code:
     <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
    <html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
        <title>Tabs Example</title>
        <!-- Ext includes -->
        <link rel="stylesheet" type="text/css" href="../../resources/css/ext-all.css" />
        <link rel="stylesheet" type="text/css" href="../../resources/css/BoxSelect.css" />
        <script type="text/javascript" src="../../ext-all.js"></script>
        <script type="text/javascript" src="../../BoxSelect.js"></script>
    
    <script type="text/javascript">
    Ext.onReady(function () {
        Ext.widget('panel', {
            title: 'My Panel'
            , height: 200
            , width: 200
            , renderTo: Ext.getBody()
            , dockedItems: [{
                xtype: 'toolbar'
                , dock: 'top'
                , items: [{
                    xtype: 'combobox'
                    , displayField: 'key'
                    , store: {
                        fields: ['key']
                        , data: [{
                            key: 'Value 1'
                        }, {
                            key: 'Value 2'
                        }]
                    }
                }]
            }]
        });
    });
    </script>
        
    </head>
    <body>
    
    </body>
    </html>
    HELPFUL INFORMATION Screenshot or Video:
    • Combo on a webserver
    • Combo on the file system

    See this URL for live test case: N/A Debugging already done:
    • none

    Possible fix:
    • not provided

    Additional CSS used:
    • only default ext-all.css

    Operating System:
    • WinXP Pro



    Trigger/Combo on a Windows 2008R2 webserver.
    trigger_web_server.PNG

    Trigger/Combo on the file system
    trigger_file_system.PNG

  2. #2
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,556
    Vote Rating
    1272
      0  

    Default

    Just to let you know I saw this but the other bug report is where the same discussion would happen.
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it! Checkout the CODE tag!

    Check out my GitHub, lots of nice things for Ext JS and Sencha Touch
    https://github.com/mitchellsimoens

  3. #3
    Sencha - Documentation Team slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,162
    Vote Rating
    257
      0  

    Default

    For what it's worth, when using Firebug Lite I see:
    Code:
    element.style {
        padding-right: 8px
    }
    When I cancel that rule the combobox looks correct.

    Also, the header text is off by what looks to be 1px. If I cancel the line-height: 15px; attrib from the rule:
    .x-panel-header-default
    {
    font-size: 11px;
    line-height: 15px;
    }

    then the server and local machine version look identical.

  4. #4
    Sencha - Documentation Team slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,162
    Vote Rating
    257
      0  

    Default

    Consider this report closed.
    I discovered that on our intranet all sites are rendered in compatibility mode (set in Group Policy) and that's forcing IE to read out msie 7 in the user agent. I can turn that off for the session and the rendering issue with the trigger fields goes away. While it's good in 4.0.7 and messy in 4.1 it's not Sencha.

    Thx.

  5. #5
    Sencha - Documentation Team slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,162
    Vote Rating
    257
      0  

    Default

    1000 apologies.
    I figured it out. In the past when auditioning code I'd take an existing file and point the ext-all.js lib to the new version and test. If all's well then I'd roll apps over to a newer version. Not a great practice if I don't also point to the latest css file, too. When no one else was complaining or could reproduce the anomalies I knew it was something I was doing, but couldn't figure out what.

    Sorry for the wasted effort looking for bugs that just weren't there. Please consider this thread closed.

Posting Permissions

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