Internet Explorer Script Error Dialog

I did that already but they still come up.  I checked "Disable script debugging" and I unchecked "Display a notificatin about every script error" but they still show up.

Tony

It will be nicer if you can resolve your script problem in your HTML rather than disable any debugging tools, it's because your front-end users somewhere else may face the same problem as you facing now. Try open your sourcecode and debug where the error comes from.

regards

here,  http://msdn.microsoft.com/library/en-us/dnscrpt/html/WebErrors2.asp
it says
> (note that checking the Disable script debugging setting will apply only to that instance of Internet Explorer):

So that appears to be a per-instance setting.  You would need to set it in your browser instance.  It looks like you might need to add a window.onerror handler (I've never done that).

Aee if you can find this setting:
    Automatically enable ASP server-side debugging on launch
in VS 7 and turn it off.

-- Dan

P.S. as  ryancys said, it's best to just fix the errors :)

Ok, well, this is not my html, script code.  It is certain sites that my users navigate to.  Although it would be nice to fix the web's script issues everywhere, i think is out of my hands.

To be kinder, gentler on my users i wanted to supress that diaog.

Go into regedit and Modify the Disable Script Debugger key to say "yes" without the quotes.  It is located in a couple of locations.
One is for the current user and one for default profiles (Used when new users log on the the computer).  If you already have user profiles already on the computer there are more entries in the HKEY_USERS\S-#-#-##\Software\Microsoft\Internet Explorer\Main.   The # signs are replaced with numbers.  
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main

HKEY_USERS\.DEFAULT\Software\Microsoft\Internet Explorer\Main

These should fix the problem.

I have searched the entire registry for "Disable Script Debugger" and changed everywhere to "yes" without the quotes and they still show up.  I do not understand what it is about this script error dialog, but i cannot seem to get rid of them popping up... guess this is a hard one, maybe this should be worth 1000 points!!!!

Tony

If you have Visual Studio 6.0 installed on a computer you would need to do the following:

This is an answer from a previous question:
In Microsoft Visual InterDev, go to Tools > Options and then "Debugger".
Un-check "Attach to programs running on this machine" in the Script section.

Also, try running the program on a computer that does not hae VisualStudio installed.  That could eliminate or confirm that it is related to debugging options set on your dev environment.
-- Dan

Dan,

Someone I know at MS told me that the script error dialog will not get suppressed because it has a yes and no button that need user interaction.  He said the only dialogs that get suppressed are error dialogs that are informational and have only one button. However, he could not confirm this to be true as of yet.

This sort of makes sense, what do you think?  Can you confirm if this is true?

Thanks,
Tony

That is not true because all Script debugger messages ask if you want to debug them(yes) or not(no).  They can be disabled.  I have done it here at our business.  Changing those registry values should have fixed it, as long as you don't have Visual Studio installed or some other related program that compiles scripts.  

Frankly to say, you STILL need to solve the source where the error comes from.To deployed the application with buggy is NOT always the best choice. Your users will definitely come back to you if they seeing same problem as you're facing now. You may contact the script developer to resolve the problem.

regards

ryancys,

As I said before these are OTHER sites, this problem exists with standard IE, my app or netscape.  The authors of the commercial sites have errors in their code.  Like I said earlier it would be wonderful for ALL sites to be perfect, but it is out of the control of my app.

I am glad you are a purist and do not like to ship buggy code, but I do not wish to either.  My code DOES NOT have a a bug, it is the sites we are going to.  SO, to make my app nicer to users I was hoping I could find a way to disable the dialog.

I guess I have stumped alot of people and came across a problem that may not have a solution.  Even the MS folks I have spoken with so far say to set the options, but it simply does not seem to work.

Thanks,
Tony

Dan,

You may have an answer to this one...  I took part of a page that causes a script error, i can send it if you like. But in any event, I have an IE/HTML based app.  If I open the html file in IE with the check boxes as talked about by all it does not display an error.  BUT, in my app and the Microsoft, MFCIE Sample App, the script errors appear.

So, my conclusion is that the IE OCX does not abide by the internet options you can set in IE.  Do you know how, or if, similiar options can be set in the MFCIE App, or my app.

Maybe this find will give some clues to all that have tried to answer, i guess this is really hard so I will up it 1000 points!!!!   Seems like a thing to do, since this has been round and round for a bit!!

Plus I really appreciate the help in uncovering the mystery!!

Tony

About 1,000,000 other people seem to be having a similar problem!
Here is a google groups search...
    http://groups.google.com/groups?q=%22Disable+Script+Debugger%22&

Here is what Microsoft has to say:
    http://support.microsoft.com/default.aspx?scid=KB;EN-US;q305389

The only people who offer a working solution describe how they had to change a registry setting (well, actually teo registry settings).  Here is one solution that shows complete VB coding:
    http://groups.google.com/groups?selm=eCOgBrt%23AHA.1852%40tkmsftngp05&rnum=6

At the bottom the poster briefly describes a different 'last resort' solution:  He loads the HTML separately and feeds it into the browser.  I suppose that would bypass the JIT (just in time) debugger's logic for (I'm guessing) installing an onerror handler.

Another thread gave me this idea:  
Sink the "Download complete" event in your control.  That will let you know if the popup occurs before or after that event.  It might be possible to add a 'window.onerror' handler of your own at that point.

Post the URL of a page that causes the problem, and I'll take a stab at winning the 1000 points.

-- Dan

Dan, I do not have an url, but i do have a script line that produces a script error that i have used for testing... I have been looking at IHTMLWindow2 methods, they do have an onerror.  I am not sure at this point how to get that event, but if you can help there, that may be a solution.

Search for DISPID_HTMLWINDOWEVENTS2_ONERROR, OLECMDID_SHOWSCRIPTERROR and Q261003.

If you think that may work, help in how to implement it would be appreciated...

Thanks,
Tony

I guess then that you've seen this:
 
     HOWTO: Handle Script Errors as a WebBrowser Control Host
     http://support.microsoft.com/default.aspx?scid=kb;en-us;261003

and the many links here:

     http://support.microsoft.com/common/canned.aspx?R=D&H=IE%20Programming%20WebBrowser%20Frequently%20Asked%20Questions&LL=kbIEsearch&SZ=kbWebBrowser

I have not re-installed VS7, so I can't experiemet with an MFC DHTML dialog right now.  But I'll look into how that code provided in the first link above can be applied to your situation later tonight or tomorrow.

-- Dan

I am on this path now...  

      MSHTML::IHTMLDocument2Ptr pMainDoc= this->GetHtmlDocument();
      _variant_t varFO =  CFunctionObject<CMfcieView>::CreateEventFunctionObject(this, OnErrorCallback, 0);

      MSHTML::IHTMLWindow2Ptr pWin;
      pMainDoc->get_parentWindow(&pWin);

      MSHTML::IHTMLWindow2Ptr pParentWin;
      pWin->get_parent(&pParentWin);

      HRESULT hr = pWin->put_onerror(varFO);

I will test it soon...

Dan,

You were going to look into a few things... let me tell you where i'm at...  I have put this code in my OnDocumentComplete:        MSHTML::IHTMLDocument2Ptr pDoc= GetMainWnd()->m_BrowserControlTop->GetHtmlDocument();
if (pDoc)
{
      _variant_t varFO =  CFunctionObject<CIEHtmlViewMain>::CreateEventFunctionObject(this, nErrorCallback, 0);
      MSHTML::IHTMLWindow2Ptr pWin;
      pDoc->get_parentWindow(&pWin);
      MSHTML::IHTMLWindow2Ptr pParentWin;
      pWin->get_parent(&pParentWin);
      HRESULT hr = pWin->put_onerror(varFO);
}

AND, added the following function:

void CIEHtmlViewMain::OnErrorCallback(DISPID id, VARIANT* pVarResult)
{
      TRACE("SCRIPT ERROR\n");
      (*pVarResult).vt = VT_BOOL;
      (*pVarResult).boolVal = VARIANT_TRUE;
}


But, it does not appear to ALWAYS get called.  Any ideas why?  I think I am on the something to catch these script errors, but it does not always seem to work.

Any help would be appreciated as this is a veri frustrating... and obviously, difficult problem!!

Thanks,
Tony