IE crashes when calling parent function

**jeffsadowski** · 09-04-2012 03:24 PM

Is it possible to move this to the javascript section of the website I don't want to cross post since it is usually frowned up on?

So I had been doing some investigating and came up with a simple page to demonstrate my problem. This has no problems in firefox or chrome and seems to effect IE only.

Below is code where javascript writes an iframe's content.
works good till you click the button in the iframe 26 times then IE
throws an error

SCRIPT28: Could not complete the operation due to error 800a001c.

At which point the iframe is blank if I press just the outside button it has no problems. Maybe it has to do that the function being called has no page to return to since it is overwritten. How should I go about fixing this?

My current work around is as follows. I create a variable firstwrite then set it to true. In my write_page function if firstwrite is true I use the open write close method and set firstwrite equal to false then any other calls I set body.innerHTML to the output this seems to work but am I suppose to do anything special when calling a parents function that changes the current iframe?

Code:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
<title>IE Crasher</title>
<script type='text/javascript'>
var mycontentdocument=null;
var count=0;

//<!--
// function to build html objects
// expected arguments=tag,data,prefs
//-->
function h()
{var tag="";
 var data="";
 var prefs="";
 for (var i = 0; i < arguments.length; i++)
 {if(i==0){tag=arguments[i];}
  if(i==1){data=arguments[i];}
  if(i==2){prefs=arguments[i];}
 }
 var retval="\<"+tag;
 if(prefs!=""){retval+=" "+prefs;}
 retval+="\>"+data+"\</"+tag+"\>";
 return retval;
}

function write_page(body)
{var output='\<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"\>\n';
 var head='\n\<meta http-equiv="Content-type" content="text/html;charset=UTF-8"\>\n'+h("title")+'\n';
 output+=h("html","\n"+h("head",head)+"\n"+h("body","\n"+body)+"\n")
// alert(output);
 mycontentdocument.open("text/html","replace");
 mycontentdocument.write(output);
 mycontentdocument.close();
}

function increment()
{var body="<input type=button value='next' onclick='parent.increment()'>\n"+(count++);
 write_page(body);
}

function init()
{mycontentdocument=document.getElementById('mycontent').contentDocument;
 if(!mycontentdocument){mycontentdocument=document.frames['mycontent'].document;}
 increment();
}
</script>
</head>
<body onload='init()'>
<iframe id='mycontent' class='fullscreen'></iframe><br>
<input type=button value='next' onclick='increment()'>
</body>
</html>

**rtrethewey** · 09-05-2012 12:27 AM

My advice would be to start over from scratch. You're having the browser go to a lot of trouble to update the page because you're relying on an <iframe>. If you used a simple <div>, you could simply change it's contents by setting/resetting its .innerHTML property and not have to construct a complete HTML document for each cycle. Something like:

Code:

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
<script type="text/javascript">

var count=0;

 function increment() {
    document.getElementById('mycontent').innerHTML = count++;
 } // end increment()

</script>
<style type="text/css">
 #mycontent { height:30px; background:#ffffd7; }
</style>
</head>
<body>
<div id="mycontent"></div>
<input type="button" value="Next" onclick="increment(); return false;" />
</body>
</html>

would do just as well.

**jeffsadowski** · 09-05-2012 02:46 PM

Thank you rtrethewey you where very helpful.

Originally Posted by rtrethewey

My advice would be to start over from scratch.

No way. The code above was just a small snippet to demonstrate the problem. however the write_page function could easily be adapted to write to a div using what you mentioned.

Originally Posted by rtrethewey

You're having the browser go to a lot of trouble to update the page because you're relying on an <iframe>. If you used a simple <div>, you could simply change it's contents by setting/resetting its .innerHTML property and not have to construct a complete HTML document for each cycle.

iframe.body.innerHTML=body was my workaround. I didn't know div had that innerHTML property. div does work much better and I can remove parent. in all my calls. I still use the h function for writing tables and such to that div.

The question still exists if setting innerHTML to a value is proper or should it be done via a method like open write close?

**rtrethewey** · 09-05-2012 06:37 PM

innerHTML is the better solution because, as I said, you don't have to reconstruct the entire document just to update one small section.

Thread: IE crashes when calling parent function

Thread Tools

Display

IE crashes when calling parent function

Thread Information

Users Browsing this Thread

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions