CellTable styles incorrectly on IE9

198 views
Skip to first unread message

drtman

unread,
Sep 24, 2011, 7:04:36 PM9/24/11
to Google Web Toolkit
If I take the example code directly from the GWT API docs for
CellTable (i.e. the code for an entry point module that creates and
displays a contact table with a manual list), the table that is
displayed has no formatting whatsoever on IE9. It is just simple left-
justified text with no styling and nothing is selectable. If I
replace the CellTable with a DataGrid, only the paging control
displays. On Chrome and Firefox these appear to work. I have tried
all combinations of styling, tried replacing the CellTable.Resources
with my own styling, etc., etc. and it never works.

Is there a trick to making the new data widgets style properly on IE9?

Juan Pablo Gardella

unread,
Sep 24, 2011, 9:14:39 PM9/24/11
to google-we...@googlegroups.com
IE9 is supported sinde GWT 2.3.0, what version of GWT are you use?

2011/9/24 drtman <drt...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.


drtman

unread,
Sep 24, 2011, 9:24:55 PM9/24/11
to Google Web Toolkit
I am using the latest, i.e. 2.4.0, and the latest version of the
eclipse plugin (just updated last night). Perhaps it's a some setting
in IE9, but I have tried turning compatibility view on/off, putting
the IE=9 meta tag in the html loader file, and a variety of other
things, but it's just broken. I am using IE 9.0.8112.16421.


On Sep 24, 8:14 pm, Juan Pablo Gardella <gardellajuanpa...@gmail.com>
wrote:
> >http://groups.google.com/group/google-web-toolkit?hl=en.- Hide quoted text -
>
> - Show quoted text -

Simon

unread,
Oct 26, 2011, 5:00:39 PM10/26/11
to Google Web Toolkit
I can confirm this bug. Not only does this affect CellTable, but
DataGrid, CellSampler, and "Cell Validation" classes. Anyone can
validate this by navigating to Google's own "GWT Showcase" at
http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable in
IE9.

Where can we officially report this bug so it gets escalated
appropriately? This is very important because I'm in the midst of a
missionary endeavor to convert to GWT at my company in lieu of
JSF(which in IMHO are much inferior paradigms for most applications),
and I'm losing traction over this! :P

Thanks in advance.
> > >http://groups.google.com/group/google-web-toolkit?hl=en.-Hide quoted text -

Patrick Julien

unread,
Oct 26, 2011, 5:20:07 PM10/26/11
to google-we...@googlegroups.com
I just tried the showcase link in IE9, it looks identical to chrome.  I can select the controls.  I don't know what could be wrong but it's working here

Jeff Larsen

unread,
Oct 26, 2011, 6:19:18 PM10/26/11
to google-we...@googlegroups.com
I got the same as Patrick. CellTable is filled with styling. 

Patrick Tucker

unread,
Mar 9, 2012, 3:07:49 PM3/9/12
to google-we...@googlegroups.com

I'm having the same problem with one of the machines at my work, but the others work fine.  Really strange, if you look at the HTML in Developer Tools, the elements that are in the TBODY element, which are supposed to be TR and TD elements, are DIV elments. 

Has anyone filed an issue? 

ItIsGoofedUp.png

Patrick Tucker

unread,
Mar 9, 2012, 3:54:51 PM3/9/12
to google-we...@googlegroups.com
Turns out someone installed Chrome Frame on this machine.  It works fine when disabled...

JoseM

unread,
Mar 10, 2012, 12:21:20 AM3/10/12
to google-we...@googlegroups.com
So then it seems that this is related to that other bug where GWT thinks the browser is Chrome since Chrome Frame is installed (but maybe not being used) and it uses the webkit specific browser code and not the Trident/IE one. (I believe the bug is more of a Chromium bug than a GWT bug).

Patrick Tucker

unread,
Mar 10, 2012, 8:55:32 AM3/10/12
to google-we...@googlegroups.com
Either way, you would think a resolution is possible, be it from the ChromeFrame team or the GWT team?

The app works fine when ChromeFrame is disable, so it seems the problem lies in GWT's detection code.

Reply all
Reply to author
Forward
0 new messages