> > Do you have a specific example? I'm curious. > Existing widgets should also work great on mobile devices, its not just about writing new widgets.
Its also not just about widgets in general. For example there is currently an issue in GWT-RPC where only IE9 has a memory leak because GWT-RPC uses eval() to parse the server response and IE9 keeps everything eval'd in memory. Slightly changing the server code and switching to JSON.parse() on the client would solve the problem, but IE6/7 do not support JSON.parse(). So to fix this issue for IE9 the server serialization needs to figure out which IE version is talking to the server and then generate different responses (either JS or JSON). Targeting different browsers on client side is easy (deferred binding) but this time the server must target different browser versions as well. So its more complicated than it could be. https://code.google.com/p/google-web-toolkit/issues/detail?id=5736 https://gwt-review.googlesource.com/#/c/2900/ I think thats a good example where IE6/7 support costs more development resources although you know that IE6/7 doesn't really play a big role anymore. Microsoft recommends to not use them anymore and 2014 they will stop supporting IE6-8 as Windows XP extended support ends in April 2014. So would you invest a lot of work today in supporting browsers whose support officially ends in less than a year? Probably not. Its a good time now to slowly phasing out IE6/7 and later IE 8 support. -- J. -- 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.
