The workaround seems to work fine :) Tested on the demo project, and it responded to everything. Ive put it on my main project and I'm pretty sure its working fine there too. (cant know 100% yet, as the history stops responding on certain functions...I suspect its due to a another part of my code crashing in though)
Are there any side-effects of this I should be aware of? Will future gwt upgrades change/effect this? Cheers, Thomas On Aug 17, 1:24 am, Thomas Broyer <t.bro...@gmail.com> wrote: > On 16 août, 16:23, Jeff Chimene <jchim...@gmail.com> wrote: > > > Is Opera supported? > > It was... until History code were reworked for IE8 (HTML5/ > onhashchange) support! > > Reported as issue 3956 (submitted too early, summary needs updating, > sorry):http://code.google.com/p/google-web-toolkit/issues/detail?id=3956 > > @twdarkflame, could you try the proposed workaround? > > > I know it's WebKit, but even so... > > Jeff, you need a refresh, Opera's using it's own rendering engine (and > JS engine BTW) known as Presto. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
