Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Rendering issues in IE7

    Hi,

    Our application integrates a whole lot of external resources (content from different domains). We have applications windows that display content from these sites in HTMLPanes in a tabbed format:

    Code:
    String contents = "<iframe name='"+id+"' id='"+id+"' width='100%' height='100%' src='"+sUrl+"'></iframe>";
    bWidget.getTabPane().setContents(contents);
    I notice that for some sites, after the window/tabbed pane displaying it is closed, it will leave a element on the UI, like an image or background. This masks content on the page.

    Have you come across similar issues like this and is there something that can be done to prevent this? reg: Content displayed in iframes in child windows should not linger on after the window is closed.

    Thanks.

    #2
    This basically suggests that the <iframe> is still there. If so, you should be able to use Firebug or another DOM inspector to find it. Or, it could be a matter of not calling destroy() to get rid of the SmartGWT component containing the <iframe>, in which case the components that are still lingering around are still visible in the Watch tab of the Developer Console.

    Comment


      #3
      Thanks, calling destroy actually fixed the issue.

      Code:
      win.addCloseClickHandler(new com.smartgwt.client.widgets.events.CloseClickHandler() {
      		    public void onCloseClick(CloseClientEvent event) {
      			DeferredCommand.addCommand(new Command() {
      			    public void execute() {
      				win.destroy();
      			    }
      			});
      		    }
      		});

      Comment


        #4
        On a similar note: I am also displaying content in iframes in a sectionstack. Minimizing/Maximizing the sectionstack causes similar rendering issues as well in IE7 i.e. elements of the content linger on the browser. Is there a way to prevent this ? Obviously, I cannot call destroy here.

        Thanks,
        Sandeep.

        Comment


          #5
          Sounds like some kind of burn-through issue which most likely depends on the contained content. You can try using the internal flag "hideUsingDisplayNone" to see if that makes the problem go away. Apply it to the HTMLFlow via setAttribute("hideUsingDisplayNone", true) when you create it.

          Comment


            #6
            Thanks !! Amazingly, this works like a charm !!

            Comment


              #7
              Glad to hear it. Please consider purchasing support so that you'll have reliable access to this kind of advice in the future.

              Comment


                #8
                I will definitely be making the case with my management. Thanks.

                Comment

                Working...
                X