@gregor If you have two (GWT) pages and page A has a tabpanel and the tabpanel has a splitpanel, then if the splitpanel is not showing and you go to the other page and back, then click the splitpanel tab, it will have gone awry again.
It also assumes that the tabpanel is aware that the tab contains a splitpanel. If the splitpanel is created on the fly depending on the situation of the user/data/time-of-day/whatever and if the tabpanel might get hidden, and/or if a disclosure panel is involved, then it all gets rather complicated @loott I don't think adding it to the rootpanel will be easy since you will have problems trying to line it up/resize it with a window resize and so on. I'm sure the GWT team didn't intentionally design it this way. They are very focused on functionality and cross-browser support but seem to have a bit of a blind-spot (maybe lack of resources for testing) when it comes to how things might be used (or even how things *are* being used). I expect they will fix it eventually - how fast is anyone's guess. There are some seemingly simple fixes that fix problems which are obviously wrong which have been around for ages. Others get sorted almost immediately. Their priorities are different to ours. Well, it's their product... Gregor's workaround should be OK if you aren't going to swap the tabpanel (or a parent) out of the DOM and back again. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
