I suppose it depends on your priority. What is your purpose in GWT generated code passing this particular html validation? Is the resulting application actually going to be more accessible if these were fixed, or is it just because somewhere says its good practice? Keep in mind the problem GWT is trying to solve, making highly efficient js code that works the same on all browsers, which means it uses whatever elements work best. While it sounds good to be "valid and standard", I don't think anything listed above really matters for an AJAX app. That said, if there's something that needlessly violates standards, then sure it should be fixed, but not at a high priority.
And if you don't like GWT using tables to lay things out, look at the new LayoutPanels, which if used as shown in the documentation mostly gets rid of tables as layout elements. jk -- 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.
