Databases
StackOverflow2013
Postsdbo
POExtJS GridPanel Scrollbar does not appear in IE7 but it does in Firefox, etc
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExtJS GridPanel Scrollbar does not appear in IE7 but it does in Firefox, etc
    text
    copied!<h1>Setup</h1> <p>I have an accordion layout containing a "properties" panel that nests two inner panels. The first inner panel holds a <code>Ext.DataView</code>, while the second panel is the <code>Ext.grid.GridPanel</code> in question. In the screenshot below, the white space containing the folder icon is the dataview, and below that is the gridpanel. </p> <h1>Problem</h1> <p>In Firefox, Chrome, and Opera, there is a scrollbar that appears when my gridpanel has an overflow of properties. It is only in Internet Explorer that it does not appear. I am, however, able to scroll using my mouse scroll button in all browsers, including IE.</p> <p><img src="https://i.imgur.com/mNjVD.png" alt="alt text"></p> <p>I've also tried removing our custom css file in case it was affecting it somehow, but there was no change in doing so.</p> <p>I'm not sure exactly what code I should show as I don't know where the exact problem is coming from but here is the code for the mainpanel and gridpanel. </p> <pre><code>var mainPanel = new Ext.Panel({ id : 'main-property-panel', title : 'Properties', height : 350, autoWidth : true, tbar : [comboPropertyActions], items : [panel1] //panel1 holds the DataView }); var propertiesGrid = new Ext.grid.GridPanel({ stripeRows : true, height : mainPanel.getSize().height-iconDataView.getSize().height-mainPanel.getFrameHeight(), autoWidth : true, store : propertiesStore, cm : propertiesColumnModel }) //Add gridpanel to mainPanel mainPanel.add(propertiesGrid); mainPanel.doLayout(); </code></pre> <p>Any help into the right direction would be greatly appreciated. Thank you.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload