RichTextArea supports a basic and an extended feature set: http://google-web-toolkit.googlecode.com/svn/javadoc/1.5/com/google/gwt/user/client/ui/RichTextArea.html
I imagine this approach was taken because the RichText capability gap was too large cross browser to feasibly emulate everything in the worst browsers. Would it make sense to take the same approach with GWTCanvas? (The vector graphics capability gap between IE6 and FF3 may also be too large to be feasibly spanned via emulation alone). For example, Client-side GChart has gained a lot of value from this relatively small subset of GWTCanvas's features: http://gchart.googlecode.com/svn/trunk/doc/com/googlecode/gchart/client/GChartCanvasLite.html Many flowsheet simulation packages could also be comfortably implemented via some such subset (plus the standard GWT Widgets, of course). If such a bifurcation allowed GWTCanvas to graduate from the incubator much faster, I think it would be worthwhile. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
