UIBinder and IE6

Michael Vogt

unread,

Mar 31, 2010, 5:30:21 PM3/31/10

to google-we...@googlegroups.com

Hello.

I would like to use UIBinder to define the layouts for my next
application. Problem is, that the client site still use IE6 as their
main browser.

Since I did not find it explicitly statet in the docs of GWT, I'd like
to ask if there are any limitations when using UIBinder regarding IE6
compatibility.

Thanks in advance,
Michael Vogt

Michael Vogt

unread,

Mar 31, 2010, 5:34:04 PM3/31/10

to google-we...@googlegroups.com

michael

unread,

Mar 31, 2010, 5:43:58 PM3/31/10

to Google Web Toolkit

michael

unread,

Mar 31, 2010, 5:47:24 PM3/31/10

to Google Web Toolkit

Hello.

Sorry for posting the question 3 times, but I got a message from
groups that my message could not be posted. Looks like this was not
the case.

Sorry,
Michael

Russ

unread,

Mar 31, 2010, 9:09:32 PM3/31/10

to google-we...@googlegroups.com

I believe Google has begun to transition away from IE6 support, though, I don't think UiBinder is incompatible with IE6 at all. If you read the documentation it explains quite well what doctypes to use.

From what I gather, GWT is for eliminating inconsistencies between browsers in a way that the developer doesn't have to worry about whether or not their app will run on IE6/7/8, among other things.

--
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.

--
Which would you rather believe in: A God that never answers you or a society that embraces you?

Thomas Broyer

unread,

Apr 1, 2010, 6:26:56 AM4/1/10

to Google Web Toolkit

UiBinder is nothing more than a code generator. All it does generate
you can code it by hand. And UiBinder does nothing more than some
setInnerHTML and/or instanciating widgets, so it doesn't change
anything re. browser support.

However, there's a general confusion with layout panels (many people
posting here about UiBinder were actually talking about layout
panels). Layout panels work fine in all GWT supported browsers
(including IE6) provided your HTML page is in standards mode (just add
<!DOCTYPE html> at the very beginning of the page). There's "just" a
bug when you use RootLayoutPanel and PopupPanel in the same app:
showing the PopupPanel hides the RootLayoutPanel; but there's a fix
for that (I don't know if it's in 2.0.3 or not; but it'll be released
by the time you'll ship your app ;-) )

The only limitation with IE6 is CssResource @sprite which does nothing
to workaround IE6's lack of transparency support in PNGs (contrary to
the Image widget). If you don't use transparent images, it'll just
work, otherwise you'll have to either live with it (transparent areas
will look opaque grey) or use workarounds, such as using a GIF for
IE6/7 (as it's done in the Mail sample app)

As for Google apps no longer supporting IE6, it's just about Google
Apps, not GWT.

Michael Vogt

unread,

Apr 1, 2010, 2:16:54 PM4/1/10

to google-we...@googlegroups.com

Hello Thomas.

Thanks for you long explanation.

> UiBinder is nothing more than a code generator. All it does generate
> you can code it by hand. And UiBinder does nothing more than some
> setInnerHTML and/or instanciating widgets, so it doesn't change
> anything re. browser support.
>

You are right, my question was not worded correctly. I guess the
question should habe been about the widgets that get used. I
understand that they are the same as I would code the layout with
Java. Correct?

Thanks for the heads up regarding the RootLayoutPanel and the transparent png's.

> As for Google apps no longer supporting IE6, it's just about Google
> Apps, not GWT.
>