Fair enough, but I'm curious to know why leaving the code that supports legacy browsers would interfere with implementing new features. For example, if you want to implement a new widget called XPanel, it think it's perfectly fine to say that this widget doesn't support IE6/7/8, and leave it up to userland to chose whether to use the new widget and how to work around it for new browsers.
Do you have a specific example? I'm curious. On Thu, May 23, 2013 at 5:54 PM, Jens <jens.nehlme...@gmail.com> wrote: > To simplify the code base and moving on (HTML 5) I would say. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
