-
24 Apr 2012 8:18 AM #1
Grids are rendered differently in upcoming versions of Google Chrome
Grids are rendered differently in upcoming versions of Google Chrome
From Chrome 18 upwards tables with table-layout:fixed are rendered differently. (Rightly or wrongly, I don't know)
This causes grids that are 'fit' to the width to spill over and some columns become inaccessible.
This problem is most evident in grid with many columns, because the border of each cell isnt being taken into account when calculating the width.
-
24 Apr 2012 8:55 AM #2
Can you please provide images that display the differences and the exact versions of Chrome that you are testing on ?
Also, can you specify if you are using 3.4?
Regards,
Scott.
-
24 Apr 2012 9:07 AM #3
ExtJs is version 3.4, the issue seems to affect Chrome 19 & 20 (any minor version).
See attached screen shot and example page. The example page is very stripped down, as it took me a while to figure out, but the styles used are straight copies of those in the ext css
Chrome 18
chrome18.PNG
Chrome 20 (notice icons are cut off)
chrome20.PNG[
-
24 Apr 2012 9:18 AM #4
Thank you for the report:
EXTJSIII-47
Regards,
Scott.
-
24 Apr 2012 11:57 PM #5
Thanks Scott.
How can I track the progress of this issue?
-
25 Apr 2012 4:31 AM #6
At this time, there is no public tracking of bug reports. You will have to check changelogs of each release.
Please feel free to ask on occasion about the progress.
Regards,
Scott.
-
25 Apr 2012 5:25 AM #7
What are the chances of a ExtJs 3 release before the next stable release of Chrome? (end of May-ish)
-
25 Apr 2012 6:20 AM #8
I have not received a date for 3.4.1 at this time. I know there is an aggressive schedule to get a release out soon now that 4.1 is GA.
Regards,
Scott.
-
16 May 2012 12:09 AM #9
Chrome 19 became stable last night, so this issue will now start to affect users.
The issue has been logged with the Chrome team, but with no response as yet. Are there any temporary solutions/shims?
-
16 May 2012 12:18 AM #10
You found a bug! We've classified it as
EXTJSIII-47
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote
