As if it weren’t bad enough we have to make exceptions and workarounds for every version of Internet Explorer out there, but as it turns out there are some differences between the two flavours of Internet Explorer which now exist: The standard 32bit and the newer 64bit.
Over the last several days I’ve been pestered by this infamous error from IE:
Message: HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)
URI: <removed – not relevant to topic>
In a nutshell, a flash slideshow module I’m using in Joomla was throwing this error, then refused to load anything further on the page. I should also note that this particular site is Error Free and works fine with ALL OTHER BROWSERS!
The first thing I searched for was the Knowledge Base reference. Gotta love Google. I found a solution and workaround rather quickly. I’ve always loved quick fixes.
Off I went to my next task thinking this issue was behind me. No so. Seems anyone using the 64bit versions of Internet Explorer are still experiencing the above error. The workaround(s) only seem to fix the 32bit versions. I’m still searching for a solution.
The specifics of the error are not the issue I’m pointing out here. Nor is the Web Site.
The point of this post is that we, as Web Developers, now have a new layer of Web Site testing to consider. Not everything at the 32bit level is going to work for users of 64bit browsers. This issue has shown me that. I’m also assuming this situation could go the other way as well. Things that work in 64bit may not work in 32bit.
I can guarantee you that for each new browser version we’ll be doubling our testing efforts.
I can also guarantee that after reading this post you’ll be running around to all your Web Sites for additional testing. (32bit and 64bit)
Let me know if you find any surprises.