You found a bug! We've classified it as
a bug in our system.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
-
Sencha User
Awesome patch!
Thanks for that quick fix, Seek!
-
Sencha User
Same problem
Hello, I have same problem and did a workaround, but if someone
can help with other solution, I'll be happy..hehe
The problem, i think, is related with vertical-scroll size, in chrome the header
do not let size for the scroll
img1-Chrome
1.jpg
img2-IE
2.jpg
It works, but is not fine...
var GridView = Ext.extend(Ext.grid.GridView, {
...
layout : function(initial) {
....
if (this.innerHd) {
if (Ext.isChrome) {
gridWidth = gridWidth - 15;
}
this.innerHd.style.width = (gridWidth) + "px";
}
-
Sencha Premium Member
Maybe someone from the development team can help Chrome developers resolve this issue?
http://code.google.com/p/chromium/issues/detail?id=124816
-
Sencha Premium Member
RowEditor fix
Does anybody have a fix for RowEditor plugin, as it is also affected by this issue?
-
Have you downloaded the latest version of Chrome? v20
Scott.
-
Sencha Premium Member
@Scott: No I don't have Chrome 20 yet, but I tried Canary build (21.0.1163.0 canary) and rendering is the same as in Chrome 19.0.1084.52 m (stable version).
-
At the moment, the fix for this is on hold as it was introduced in chrome and recognized as a problem by their developers. When a decision is made, we will proceed.
Scott.
-
Sencha User
CSS Fix needed
Please, take a look at https://code.google.com/p/chromium/i...tail?id=124816, the last comments.
There is a bug in webkit and they fixed on Chrome 21 (Canary).
But it doesn't make the Ext grid render correctly by itself, this CSS is needed:
@media screen and (-webkit-min-device-pixel-ratio:0) {
.x-grid3-cell
{
box-sizing: border-box;
}
}
So, Chrome 21 + this CSS makes the grid render correctly again.
-
Thank you for the additional information. I have posted it to the bug report.
Scott.
-
Touch Premium Member
+1 Since there is no public tracking of bug reports, I'm subscribing to this thread; hopefully pertinent information concerning this bug will be posted here as well.