Hi Gregory, The common thing between all the widgets that do implement the HasHTML interface is that they are all widgets that contain flat HTML as their innerHTML. This is also true for the HTMLPanel, however, the HTMLPanel also supports adding widgets to its innerHTML, which could cause problems when calling getText() or getHTML() and expecting a flat and unchanging HTML structure to be returned.
Aside from that, it would seem logical for the HTMLPanel to implement the HasHTML interface, if with the possible caveat mentioned above. Feel free to create a report for this on the Issue Tracker to get some of the UI team to consider the change. Before doing that though, could you elaborate a little more on your use case for having the HTMLPanel implement the HasHTML interface? There may be other ways to solve the problem depending on what you're trying to do. Issue Tracker: http://code.google.com/p/google-web-toolkit/issues/list Hope that helps, -Sumit Chandel On Fri, Jul 31, 2009 at 2:18 PM, Gregory Kanevsky <[email protected]>wrote: > > It seems very logical - almost obvious to me or what I am missing? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
