It turns out it was easier to fix the specific case this broke in client code (a test that ended up passing null for a URL).
Which raises the question, should Image gracefully handle "null" for URLs, or should the API docs clarify that non-null values are expected? Is there a convention for handling nulls in the GWT API? Thanks, --xtof On Mon, Jun 6, 2011 at 15:39, <[email protected]> wrote: > lgtm > > > http://gwt-code-reviews.**appspot.com/1443814/<http://gwt-code-reviews.appspot.com/1443814/> > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
