Results 1 to 5 of 5

Thread: Ext.ux.IFrame initialization problem

  1. #1
    Sencha User
    Join Date
    Aug 2011
    Posts
    69
    Answers
    1

    Default Ext.ux.IFrame initialization problem

    I'm going crazy over this issue: when I add panel with iFrame to my viewport all works fine for the first time.
    But when I replace content of viewport with other application view, and then go back to the one with iFrame, it will fail to initialize.
    There are no errors, I can't find anything looking through both iFrame code and Ext, but the iFrame object looks different:


    Properly initialized iFrame object:
    i-ok.PNG

    iFrame object after it was created again (after original viewport content was destroyed and recreated using Ext.create and "add")
    i-fail.PNG

    I can destroy and create this panel as many times I want when in the initial viewport, but after replacing the content, iFrame creation gives this strange result. Any hints? (btw - all other panels with tree, grids etc work fine at those viewports, so its just the iFrame panel that fails.)

  2. #2
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985
    Answers
    506

    Default

    Could be a bug. Are you able to post a test case that reproduces the issue?

  3. #3
    Sencha User
    Join Date
    Aug 2011
    Posts
    69
    Answers
    1

    Default

    I have made a JSFiddle with "quick and dirty" equivalent but "unfortunately" this example works fine....
    So I will have to track down what is the difference here... and its certainly not easy to find.
    In my case it would "crash" when you go from View 1 - > view 2 and back to view 1...

    http://jsfiddle.net/maciejzabielski/e4mZe

  4. #4
    Sencha User
    Join Date
    Aug 2011
    Posts
    69
    Answers
    1

    Default

    It seams that I have finally found the problem and it was not related to iFrame.

    Problematic "view" contained method that had several "this" calls in it. We are using message bus to notify components of changes. After recreating the view, "this" was pointing to old destroyed component.

  5. #5
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985
    Answers
    506

    Default

    Glad to hear you tracked it down, and thanks for taking the time to post the follow-up.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •