What’s the Problem with Internet Explorer?

Okay, this is pretty technical. The designers of Internet Explorer® include restrictions on the placement of certain types of code, such as JavaScript, or the introduction of security access files (htaccess) outside of the <header> tag in the HTML markup for a site. That’s okay with sites that are hand-coded.

Another reason, or excuse, for this conduct is that a component plugin starts to parse the code before the Web page is fully loaded, causing a null exception in the DOM (Document Object Model).

Many managed content sites, including ours, depend upon, and use, modular components or plugins. These code elements often have their own style sheets, JavaScript, and access controls. Since these occur outside of the </header> tag—because they are not “called” until the link to the element is clicked—Internet Explorer either returns a message saying that it cannot open the site or just leaves the area blank. (Look at the URL given for the “site;” it will be the Web address for the component you tried to open.)