Another (definitely 'Breaking') change in 1.5.2 from 1.5.1 is that
public final native String getAttribute(String name) /*-{
return this.getAttribute(name);
}-*/;
in Element has become
public final native String getAttribute(String name) /*-{
return this.getAttribute(name) || '';
}-*/;
i.e. if the attribute does not exist, then for some reason, you don't get
the expected null, you get an empty string.
Could someone from Google explain why there has been this diversion from the
path of 'least surprise'? What suddenly became so wrong with returning what
JS gives you? Could you mention it in the release notes as a breaking
change? It breaks any number of my apps, all of which check for null,
because that's what you used to get.
As for the other, unfixed problems, surely a release candidate is a
candidate for being released. If it passes, it gets released. If it doesn't
pass you change it and put out another release candidate. I'm a bit
surprised that 1.5.2 is 'official'.
Ian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
