Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IE 6 Javascript Errors 1

Status
Not open for further replies.

clarkmurray

IS-IT--Management
Nov 9, 2002
35
US
I have created and market a training product that uses IE for menus and then uses javascript to launch Flash movies in a separate browser window. I have a customer who says he that when he clicks on a link to launch a movie, he receives an "Error on Page" message on the status bar and the Flash movie will not launch. The strange thing is he says he is using IE 6.0 and XP. I also use IE 6.0 and XP and have never had any problems. I have several hundred customers now, and no one else has reported any problems either.

I realize this is a fairly general statement of the problem, but I have no idea how to begin troubleshooting a bug like this. I searched the Microsoft knowledge base and didn't come up with anything.
 
Depending on how browser-proficient this customer is you could get him to up the level of alerts that IE provides on Javascript errors. Or if you can get out on site, do it yourself. That way you will be able to narrow down the error(s) to the exact line(s) of code causing them.
 
Here's a link to the site. That's probably better than posting the code.


I, or anybody else, can test the site. Just click on one of the menu buttons on that page. But as I said the real problem is I can't recreate the error using IE 6, so it's not a question of trying to debug it.
 
tell that customer to double-click the yellow script error icon in the bottom left corner of his browser and tell you what the error is.


=========================================================
try { succeed(); } catch(E) { tryAgain(); }
-jeff
 
I'm using IE6 on XP and it's ok.

Better to use-

<a href=&quot;#&quot; onclick=&quot;openmovie('Introduction00000');&quot;>
 
OK, here's the report I received from the user:

>On the Demo page, I used the &quot;Tracks Pane&quot; navigation
>button for the test.

>As the cursor is hovered above that link, the The Links >Bar reads: javascript:eek:penmovie(Tracks_Pane00000')

>When the link is selected, the Links Bar reads: &quot;Error on
>page.&quot;

>Double clicking the Links Bar at that point brings up
>an &quot;Internet Explorer&quot; window, which reads: &quot;Problems >with this web page might prevent it from displaying
>properly or funtioning correctly.&quot;

>The &quot;Details&quot; are:

>Line: 24
>Char: 3
>Error: 'moviewin.window' is null or not an object.
>Code: 0
>URL:
If anyone can reproduce that (I can't) and/or tell me where to look next, I'd appreciate hearing about it.
 
still works fine for me, but i would suggest changing openmovie() to this (several redundant references to &quot;window&quot; have been removed):

function openmovie(url) {
if (!moviewin && !moviewin.open && moviewin.closed) {
moviewin = window.open(&quot;Flash_Main.htm&quot;,url,'toolbar=0,location=0,directories=0,status=0,menubar=0,scrollbars=1,resizable=1,height=654,width=820');
moviewin.focus();
}
else {
moviewin.name = url;
moviewin.location.reload();
moviewin.focus();
}
}


=========================================================
try { succeed(); } catch(E) { tryAgain(); }
-jeff
 
if (!moviewin && !moviewin.open && moviewin.closed)

I would leave out ...'&& moviewin.closed' because you are asking if(!moviewin...

meaning that the window variable does not exist, therefore it cannot be closed if it does not yet exist.
 
yeah, it should be

if (moviewin && moviewin.open && !moviewin.closed){
moviewin.name = url;
moviewin.location.reload();
moviewin.focus();
}
else {
moviewin = window.open(&quot;Flash_Main.htm&quot;,url,'toolbar=0,location=0,directories=0,status=0,menubar=0,scrollbars=1,resizable=1,height=654,width=820');
moviewin.focus();

}


=========================================================
try { succeed(); } catch(E) { tryAgain(); }
-jeff
 
I am a user of XP and IE 6 who has the same problem as the original customer. This error applies to ALL Javascript links on all web pages, not just to ones in CLARKMURRAY's coding.
 
Yes, I've been into TOOLS-INTERNET OPTIONS; both ADVANCED and SECURITY-INTERNET-CUSTOM and enabled everything I could find. I have been trying to solve this for a while, looking into several forums and PC help sites. Many users have this problem, but nobody has an answer.
 
All of this interest (and BTW, thanks to everyone for your commments) prompted me to go back to the Microsoft knowledge base. And, by golly, there is something there after all:

support.microsoft.com/default.aspx?scid=kb;[LN];281679

Since I don't have the problem, it doesn't do any good for me to apply the procedure recommended there. However, hnathan, if you could give it a try that would be great.
 
I've worked with Q281769 and gotten thru the RUN REGSVR32 xxx.DLL steps without fixing the problem. I've got a mental block about messing with the REGISTRY so I haven't found out how to &quot;verify that the following registry values are present...&quot; step. Is there a safe way to do it without changing the registry?
 
I don't claim to be an expert on the registry, but for what it's worth:

You can certainly verify whether the registry values mentioned in Q281769 exist or not without any risk by searching on the key or a portion of the key.

If you need to change anything, the standard Microsoft caveat applies: Back up your registry first. The help text gives a pretty good explanation about how to do that.

That being said, I was unable to find those values in my registry and I don't have the problem. Don't know what to make of that.
 
I think that Q281679 does not apply to the problem that involves only non-working Javascript links. I have no problem with URL links or email hyperlinks, only with Javascript links.
 
I guess you should tell your client to dump IE and download it again.
 
I agree that the only way to solve this Javascript link error is to reinstall IE. Instead I'm trying a browser recommended by a friend - Mozilla Firebird. So far it's working great, it's fast (with XP and Cable Broadband) and has never frozen or given me any problems. I think I'll stick with it until MS comes out with a new version of IE.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top