Hey, Rick.

 

Yes,  the IFrame component calls BrowserManger.init() before trying to
get the url property.  Actually it calls ".initForHistoryManager()".  I
changed it to plain init(), but still, without history enabled in the
wrapper, the .url property is always null.  I need to create a simple
test app, to verify that I do not have something else going on.

 

I am going to hack the code in the short run, using
Application.application.url, which should work as long as the wrapper
and swf are in the same domain.

 

I also must admit that I have not fully analyzed the functionality that
the problem code is providing, something about cross-domain checking,
which I do not think is important in my situation.

 

Thanks

Tracy

________________________________

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Rick Winscot
Sent: Wednesday, November 12, 2008 2:26 PM
To: [email protected]
Subject: Re: [flexcoders] IFrame, BrowserManager, HistoryManager errors.

 

It's always a good idea to do a quick null check + init before you start
touching BrowserManager...

if ( BrowserManager.getInstance().url == null )
BrowserManager.getInstance().init(); 
Are you following this pattern and still having the errors?

Rick Winscot



On 11/12/08 1:29 PM, "Tracy Spratt" <[EMAIL PROTECTED]> wrote:

        
         
        
        I am trying to use Alistair Rutherfords IFrame component in a
Flex 3 app and have a a couple issues (one with fix).
        
        First, unless I enable history management in the wrapper, the
IFrame component throws an error because BrowserManger.getInstance().url
is null.  Is this to be expected, that BrowserManager requires history
enabled?  I really do NOT want history management, but  I see that
History IS enabled on all of the Iframe examples.  I think can solve
this by modifying Iframe, but want to verify my observations first.
        
        Second, if I enable history, then the Iframe component works,
but in IE 6, I get a script error from the history.js script at the line
that calls "getHistoryFrame()", because that returns null (return
document.getElementById('ie_historyFrame');)  For some reason the
ie_history frame is not getting created.  Firefox is ok.
        
        FIX FOR SCRIPT ERROR FOUND! There is a line in history.js that
is commented out: iframe.src = historyFrameSourcePrefix; Uncommenting it
fixes the problem. This appears to be an issue with IE6.
        
        Tracy
         
            

 

Reply via email to