Kyle, Can you hardcode the onclick="window.location.reload();" method in the "OK" button, so it should still work even if the GWT frontend is hosed?
Sincerely, Joe On Jan 11, 8:56 am, Kyle Baley <[email protected]> wrote: > We've gone Thomas's original suggest route of informing the user. But in > our original pass at this, we threw up a dialog with an OK button on it. It > said something to the effect of "There's a new version. Please log in > again". Clicking OK is intended to log the user out and forcibly refresh > the page. > > What we're finding is that for the code-splitting case, the dialog does > indeed come up but the whole page becomes unresponsive afterward. That is, > you can't click the OK button. I've verified that this happens regardless > of whether we put a dialog up or not. Nothing on the page is clickable at > all. Wondering if this is what others see as well and if so, if there's a > way around it. -- 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.
