Opened 9 years ago
Closed 8 years ago
#14908 closed defect (patchwelcome)
dojox.grid.DataGrid autoHeight & noSroll Bug
Reported by: | fbos | Owned by: | Evan |
---|---|---|---|
Priority: | undecided | Milestone: | tbd |
Component: | DojoX Grid | Version: | 1.7.2 |
Keywords: | Cc: | Brian Arnold | |
Blocked By: | Blocking: |
Description
Hello Guys,
I've found an Issue using Dojox.grid.DataGrid?.
I've got this little sample to show you guys what i mean:
<span dojoType="dojo.data.ItemFileReadStore" jsId="jsonStore" url="../../../dijit/tests/_data/countries.json"> </span> <h5>Locked views specified with tables and colgroups</h5> <table dojoType="dojox.grid.DataGrid" store="jsonStore" autoHeight = "true" rowsPerPage="30" query="{ name: '*' }" style="width: 600px;" rowSelector="20px"> <colgroup span="1" noscroll="true" width="300px"></colgroup> <colgroup span="4"></colgroup> <thead> <tr> <th field="name" width="auto">WERT Country/Continent Name</th> <th width="100px" field="population">Population</th> <th width="100px" field="area">Land Mass</th> <th width="100px" field="timezone">Time Zone</th> <th width="5em" field="type">Type</th> </tr> </thead> </table>
Now I've got two different Graphical Presentation in the Mozilla Firefox and Internet Explorer. The Problem in this sample is, that the horizontal scroll bar inside the Internet Explorer is misplaced. The Firefox shows it the right way:
Here is a Screenshot of the Firefox, the right way!
Now here is the Internet Explorer which won't do it the way i want it...
So here is what happen if you are going to scroll the DataGrid? on the vertical scrollbar.
If there are any solutions for this Bug, please give me Information about this Issue.
Greatings fbos
Change History (4)
comment:1 Changed 9 years ago by
Component: | General → DojoX Grid |
---|---|
Owner: | set to Evan |
comment:2 Changed 8 years ago by
Cc: | Brian Arnold added |
---|
comment:3 Changed 8 years ago by
comment:4 Changed 8 years ago by
Resolution: | → patchwelcome |
---|---|
Status: | new → closed |
As an update, we recently ran into this bug. It turns out that it's dependent on the browser being in quirks mode. When a doctype is in play and the page is rendering in standards mode, this bug does not manifest.