"An Unhandled exception ('Object doesn't support this property or method') occured in iexplorer.exe [3496]."
When I uninstall the same, I stop getting the exception.
Please suggest.
Same problem, everytime I tried to open a we page, with Visual Studio I got the following information:
The error comes from this JScript code, when trying to set:
collSelectors.item(i).SetQuirksMode(true);
i = 0;
collSelectors.item(0) -> tagName : "BODY"
I tried to reboot, uninstal, desactive all Add-ons with no success.
// SelectorAPI member functions --------------------------------------------------------------
function ParseDoc(doc)
{
var aRules = GatherRulesFromDoc(doc);
collSelectors = parser.Parse(aRules);
// Set quirks mode if necessary
if("BackCompat" == doc.compatMode)
{
for(var i = 0; i < collSelectors.Count; i++)
{
collSelectors.item(i).SetQuirksMode(true);
}
}
}
I've had the same problem for the pas few weeks - continually get the following msg box:
title: Just-In-Time Debugging
An exception 'Runtime Error' has occurred in Script.
Then a list of possible debuggers, eg: Microsoft Script Editor
The message box continually appears (when clicking No), until I relent and click yes - which of course loads the script debugger. The following line is causing the "runtime error", eg: // SelectorAPI member functions --------------------------------------------------------------
function ParseDoc(doc)
{
var aRules = GatherRulesFromDoc(doc);
collSelectors = parser.Parse(aRules);
// Set quirks mode if necessary
if("BackCompat" == doc.compatMode)
{
for(var i = 0; i < collSelectors.Count; i++)
{
collSelectors.item(i).SetQuirksMode(true);
}
}
}
One partially satisfying "fix" is to completely disable the "Machine Debug Manager" service. I'm not sure what the implications are, but seems to fix the current IE instance (only).
Same problems here.
What is weird is that IE Developers Toolbar has been just released under 1.0 non-beta, and this offending bug is still here!
I have 2 PC aonfigured almost the same, the toolbar is working on one PC but not working on the other.
The only apparent difference betweeb my 2 PC is that in the failing one i have VS2005 side-by-side with VS2003.
Can this be THE relevant difference that make toolbar to crash I suspect that VS2005 carrying some modification
to machine debug monitor that badly interact with this toolbar.
Please help !!!!
I have the same issue, and am also responding in hopes the issue will be addressed, in either a way to remove the Just In Time debugger from popping up or in a patched version of the Developer Toolbar. Where can we get feeback to the dev team responsible for the developer tools
Come on MS! :-(
There is obviously a common problem here....where is the solution
Yes, I totally agree, I want a fix!
Anyway, in the meantime I think I use the hack.
SpecialChem wrote:
Same problem, everytime I tried to open a we page, with Visual Studio I got the following information:
The error comes from this JScript code, when trying to set:
collSelectors.item(i).SetQuirksMode(true);
i = 0;
collSelectors.item(0) -> tagName : "BODY"
I tried to reboot, uninstal, desactive all Add-ons with no success.
Code Snippet// SelectorAPI member functions --------------------------------------------------------------
function ParseDoc(doc)
{
var aRules = GatherRulesFromDoc(doc);
collSelectors = parser.Parse(aRules);
// Set quirks mode if necessary
if("BackCompat" == doc.compatMode)
{
for(var i = 0; i < collSelectors.Count; i++)
{
collSelectors.item(i).SetQuirksMode(true);
}
}
}
vikikov wrote:
SpecialChem wrote:
Same problem, everytime I tried to open a we page, with Visual Studio I got the following information:
The error comes from this JScript code, when trying to set:
collSelectors.item(i).SetQuirksMode(true);
i = 0;
collSelectors.item(0) -> tagName : "BODY"
I tried to reboot, uninstal, desactive all Add-ons with no success.
Code Snippet// SelectorAPI member functions --------------------------------------------------------------
function ParseDoc(doc)
{
var aRules = GatherRulesFromDoc(doc);
collSelectors = parser.Parse(aRules);
// Set quirks mode if necessary
if("BackCompat" == doc.compatMode)
{
for(var i = 0; i < collSelectors.Count; i++)
{
collSelectors.item(i).SetQuirksMode(true);
}
}
}
The problem is also occuring in IE 6. The old toolbar worked ok, the new one causes an expection when moving to every new page.
Removing the toolbar fixed the problem.
I also have VS2003 and VS2005 working side by side.