CODEWITHSUNDEEP
javascripterror-handlinginternet-explorer-6
Justin
Justin

Reputation: 86749

In what situation would document.open() return null?

I'm trying to understand an intermittent script error that I am seeing in a JavaScript intensive thin-client application running under Internet Explorer 6 and Windows XP. The root cause of the problem is that the following function call returns a null value (however it does succeed without an error):

var doc = targetWindow.document.open("text/html","_replace");

Where targetWindow is a window object.

Neither targetWindow nor targetWindow.document is null and so I'm struggling to understand why this call would return null. My interpretation of the documentation is that this method shouldn't ever return null.

This code has been unchanged and working perfectly for many years - until I understand why this is happening I'm not sure either how I might handle this, or what might have changed to cause this to start happening.

What might cause this function call to return null?

Upvotes: 8

Views: 510

Answers (2)

robert petranovic
robert petranovic

Reputation: 341

document.open() does not have any parameters by W3C standard. Check out this link: http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-72161170

I recommend you to use W3C documentation instead of Microsoft's one because with W3C you are sure it works on all modern browsers, while Microsoft is well known for adding extensions that, of course, works only in their own products. It's called EEE (Embrace, extend and extinguish).

Simply use document.open() without arguments. There are ways to manipulate user history, but that's called bad programming practice. History is user's private data and web application should not try to manipulate it.

Upvotes: 0

Chris Pietschmann
Chris Pietschmann

Reputation: 29905

According to the documentation you should be passing "replace", not "_replace". Try this instead:

var doc = targetWindow.document.open("text/html", "replace");

Since you say your code has worked for years, then it is likely that something has changed and the above suggestion may not be the issue. However, it is still worth a try.

Have you changed any js files / libraries you are using in your application lately? Also, are you using any browser plugins within the page? It is possible that a newer version of either of these could be somehow affecting your call to "document.open".

Upvotes: 1

Related Questions