On Sunday, September 1, 2013 7:28:36 AM UTC+2, Matthew Dempsky wrote:
>
> I'm going through @Deprecated methods in GWT working on refactoring 
> Google's code base to avoid them, and I notice there's a deprecated 
> DOM.getAttribute(Element, String) method that recommends to use 
> DOM.getElementProperty(Element, String) instead... but they both just call 
> Element.getPropertyString(String), so why aren't we recommending people to 
> call that directly and bypass the DOM static helpers?
>

Legacy.

Most of the DOM class is just legacy, back when com.google.gwt.dom didn't 
exist yet and all we had was c.g.g.u.c.DOM and c.g.g.u.c.Element. I think I 
once proposed deprecating the DOM class but was told some things had no 
equivalent elsewhere so it was a bad idea; there's also the problem that 
many widgets still use c.g.g.u.c.DOM and have never been migrated to 
c.g.g.dom.client.Element equivalents.

I think we can now safely remove getAttribute and start deprecating other 
methods of c.g.g.u.c.DOM (e.g. getElementProperty)

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to