I've found that with the IE developer tools, you need to refresh the DOM view within the tools (there's a refresh icon in the HTML view section). The view doesn't seem to take the JS changes to the page into account initially. (And sometimes you never see CSS that GWT injects, but that's off-topic.)
BTW, I ran your code and it worked fine in IE-7-10 as provided by the dev tools in IE10 (I just had onCommand do an alert with the two values), so maybe the issue is further down the line. On Friday, June 21, 2013 8:40:12 AM UTC-4, GWTter wrote: > > IE has had developer tools built in as far back as version 8, just press > F12. If you're working with <=IE7 then: IE dev > tools<http://www.microsoft.com/en-us/download/details.aspx?id=18359>. > Although it may work in other browsers or on the other anchor you want to > see exactly what is or isn't occurring so you can narrow the scope of the > issue, else it's a blind guessing game. I would put an alert or println in > the onClick method to see first if the click is even registering for the > first button, this will aid you in your analysis and you can then proceed > from there. You haven't posted the onCommand method so we have no idea if > the click is even registering in the first button case. > > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
