In more complex cases, however, we’ll need more information.
#JAVASCRIPT IEXPLORER HOW TO#
Selecting Visual Studio and clicking the yes button will open Visual Studio and highlight the code that is the cause of the problem.įor relatively simple errors, such as the one in the example above, just seeing the actual cause of the error highlighted is probably enough for us to work out what has gone wrong, and how to fix it. Now when we load that up into the browser instead of the tiny icon in the status bar IE will prompt us to open a debugger. The code below tries to call a function that doesn’t exist: functionDoesNotExist() From that point on everything is the same. Instead of IE prompting you to open the debugger, as it does in the examples below, you’ll first need to create a project and then start the debugger yourself.
#JAVASCRIPT IEXPLORER FULL#
You can also use the free Web Developer Express Edition if you don’t own a full copy of Visual Studio. After changing those settings and restarting IE, we’re ready to start debugging.Īll of the following examples show Visual Studio 2005, but the same applied to 2008. Enable the third option if you’d like the JavaScript error dialog to pop up automatically instead of being displayed as a small icon in the status bar. If you also want to debug scripts in other contexts (such as Outlook) then disable the second option. Script debugging in IE needs be enabled, which requires us to disable the first option out of the three. The image below shows the default IE6 settings, with the three settings we’re interested in highlighted. To enable JavaScript debugging in IE we need to change some default settings, which can be accessed from the Tools> Internet Options menu, and then the Advanced tab. Fortunately, with the help of Visual Studio and by changing a few IE settings, we can make it much easier on ourselves. Your best bet is to make a note of the line and column number of the problem and then look that up in the source code. Unfortunately the detailed error message can be quite cryptic, and probably not too much help in diagnosing the actual problem. Extremely easy to miss! Double clicking on this icon will display a popup, and if you then click the “Show Details” button you’ll get the actual details of the JavaScript error. When a JavaScript error occurs, IE6’s default behaviour is to display a small error icon in the status bar.
To make things worse, IE6 is extremely bad at helping developers diagnose problems. In the mean time though many of us have to make sure our sites work in this awful browser. With more and more users switching over to newer alternatives such as IE8, Safari and Firefox hopefully support for IE6 can be dropped sooner rather than later. What “just works” in the majority of browsers will almost always require hours of tweaks and workarounds to get it working in IE6. It’s hard to work with and support, but with a few solid techniques, you can make the process less painful. Microsoft’s Internet Explorer 6 is almost universally hated by web developers.
0 kommentar(er)
