[3.0.x, 3.1.1] ux.ManagedIFrame 2.x

[hendricd]

@Dave--
Depending on what this means:

2. Modify that iframe by adding in HtmlEditors at various points. (via rendering to specific DIVS in the iframe html.

Rendering HTMLEditors into the child IFRAME is going to render IFRAMES within IFRAMES. You can likely render, but the key listeners for those nested editors are not bound to the correct document context. Ext does not support targeted-event-binding (per document). It will only handle events for the document context in which Ext was loaded.

Why not render an HTMLEditor(it is an iframe) into a regular Ext.Window instead? Is there a compelling reason to nest multiple frames for editing?

Second the possible bug:

I noticed that in the multidom.js at line 100, the line is:

if(el = docCache._elCache[dom.id]){

Shouldn't the equals be a compare operator and not an assignment operator? (ie. '==' instead of '=')

No. That is coded as intended (it handles the assignment AND asserts a value at the same time.

[Dave.Sanders]

The application is a content management system where I'm trying to pull in the template page, which is fully described HTML, including stylesheets, etc, and replace key portions of the template with panels. (actually I misspoke, I'm not putting htmleditors in there now - those will be in a dialog)

So, I'm trying isolate the page template from the rest of the ext app so that CSS doesn't interfere.

I'm doing some debugging and found something interesting - if I put in a break point in multidom and loop through the code, it works. If I remove the breakpoint then it doesn't. This leads me to believe that I'm doing something in the wrong order and something isn't ready when it needs to be - but by delaying it it works.

Now that I've changed from using embedded HTMLEditors, I think I'm going to do some other HTML trickery before the iframe is loaded to link the template panels back to my code via other JS functions. So this question is probably moot besides an academic exercise.

Re: the asserts -yeah, I see that now, not a pattern that I tend to use just because it prompts questions from people like me. and it could cause you debugging headaches later.

[hendricd]

I would recommend you load either miframe.js or miframe-debug.js from the /builds directory. Things are arranged properly there.

[Tinki]

Using IE8 and script looking like

<script type="text/javascript" src='js/ext/miframe_2.js'></script>
...
<iframe id="divId"></iframe>
...
<script type="text/javascript">
Ext.onReady(function(){
var MIF = new Ext.ux.ManagedIFrame.Element("divId");
MIF.disableMessaging = false;
MIF.on('message', function(){
  alert(1);
});
MIF.setSrc("test.html");
MIF.on('message', function(){
  alert(2);
});
sendMessage("blablabla"); // <- This line causes error "Object expected"
});
</script>

Contents of test.html:

...
<script type="text/javascript">
  Ext.onReady(function(){
    sendMessage("blablabla"); // <- The same "Object expected" error
  });
</script>
...

[Tinki]

Why can

sendMessage("blablabla");

cause "Object expected" error?
Doesn't depend if executed in IFrame or in Host window.
IE8, Ext 3.0.1, MIFrame 2.0.1

[Tinki]

Dealed with "Object expected" error - need to work with frame when "documentloaded" event fired. But messaging still don't work. Does anybody have any living example of messaging (the one from FAQ in not working)?

[mschwartz]

@agalue --

REST? JSON only? hmm? A bit contra, no?

I'm not a big fan of REST (POST, POST, POST!)

However, take a look at CouchDB. Aside from it being very interesting for what it is, the API is REST though everything you POST is JSON and everything you GET is JSON, too.

[Tinki]

Still working around creating of MIFrame, which child page would have "sendMessage" method. Seems that child is ordinary IFrame and it doesn't understand sendMessage("..."). Seen some code for "onerror" event in IFrame - does it parse exception on child frame and converts it to message?
Will appreciate any messaging example, working under ExtJs 3.0.3 IE8.

[agalue]

Hello all,

I'm using ManagedIframe to show a PDF using submitAsTarget and it works great on FireFox, Safari and Chrome using browser's Acrobat Plugin (on windows) or Preview plugin (on mac).

But, with IE8 it shows HTTP ERROR 405: Method not allowed. The exact message is:

"This error (HTTP 405 Method Not Allowed) means that Internet Explorer was able to connect to the website, but the site has a programming error."

Is the PDF rendering with submitAsTarget supported in IE8?
Any workaround on this?

[agalue]

Hello all,

I'm using ManagedIframe to show a PDF using submitAsTarget and it works great on FireFox, Safari and Chrome using browser's Acrobat Plugin (on windows) or Preview plugin (on mac).

But, with IE8 it shows HTTP ERROR 405: Method not allowed. The exact message is:

"This error (HTTP 405 Method Not Allowed) means that Internet Explorer was able to connect to the website, but the site has a programming error."

Is the PDF rendering with submitAsTarget supported in IE8?
Any workaround on this?

Sorry, it was my fault... please ignore my last post.

I had a problem in my own code, the ManagedIFrame with PDF/submitAsTarget works as expected on IE8 ....