Predefined constants for DOM & CSS attributes about gwt HOT 12 CLOSED

I think this is something that needs to exist for both DOM and CSS attributes (both
names and values in many cases).  There are a lot of ways to make mistakes: both
simple typos and more subtle issues such as "float == [cssFloat | styleFloat]" and
"for == htmlFor".  These mistakes can be really hard to catch in practice, because
failures are often silent.

Here is a first attempt for the CSS Attributes. It uses a CSS.gwt.xml for different
implementations to work around the browser 'float' differences, which hides that
problem for the user of this CSS class. Let me know if this is a useful contribution.

@jgw: Is this one done now?

We recently added a set of properties to the Style object (as enums, using a pattern
known to compile efficiently). I'm going to mark this only as "started", because we
need to come back through and finish the set of style properties.

Interresteing, but it looks like every one can see you problems

You might want to consider looking at issue 4238:
http://code.google.com/p/google-web-toolkit/issues/detail?id=4238

Fixed, e.g. you can write code like this:
  element.getStyle().setOverflow(Overflow.HIDDEN);

Better yet, use UiBinder to write your HTML in the .ui.xml file and use Eclipse's CSS
code completion with CMD/CTRL-SPACE.