Great news, While doing so, also take a look at the IFrame behind the dialog trick.
I had to disable that trick because in a HTTPS environment we were experiencing 0.5 seconds delay to show Popups. I was using the PopupPanel class to implement a custom rendering of a ComboBox widget and every instance added to the DOM tree would result in 0.5 seconds lost. Our GUIs use a lot of these ComboBox widgets so it was taking minutes to show! In IE7 there is no need to do this anymore. In our case I did not even need it in IE6 since we were not using widgets that would cause the PopupPanel to be intersected with other widgets underneath. David On Mon, Apr 20, 2009 at 5:07 PM, Joel Webber <[email protected]> wrote: > Thanks, David. I'll look at this as part of the process of supporting IE8 > and cleaning up IE7 ImageBundle support. > > On Mon, Apr 20, 2009 at 4:19 AM, stuckagain <[email protected]> wrote: >> >> Dear GWT-contributors, >> >> I create a bug report on ImageBundle here. >> http://code.google.com/p/google-web-toolkit/issues/detail?id=3573&sort=-id >> >> After doing some extra investigation I noticed 2 things: >> 1) When I use Image(<url>) instead of an ImageBundle my example app >> leaks as well. >> 2) If I use Image.prefetch(<url>) then the Image(<url>) does not leak >> anymore >> >> I read about the memory leak and memory usage blaming the Alpha >> blending technique in IE6/IE7 and also the clipping settings. But how >> come that the Image.prefetch which loads the same PNG with alpha >> channel does not leak... and why does ImageBundle and Image without >> prefetch not use the same tricks as done in prefetch ? No need to >> start using VML or other tricks then. >> >> David >> >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
