{"id":306,"date":"2003-12-03T00:08:35-05:00","date_gmt":"2003-12-03T08:08:35+00:00","guid":{"rendered":"http:\/\/peterjanes.ca\/wordpress\/?p=306"},"modified":"2003-12-03T00:08:35-05:00","modified_gmt":"2003-12-03T08:08:35+00:00","slug":"hulk-smash","status":"publish","type":"post","link":"https:\/\/peterjanes.ca\/blog\/2003\/12\/03\/hulk-smash\/","title":{"rendered":"Hulk&nbsp;smash"},"content":{"rendered":"<div class='e-content'><p>How bad is this: I finally tracked down a problem some IE users were having with <a href=\"http:\/\/www.sirens3.com\/\"><code>sirens3.com<\/code><\/a>, and discovered that it&#8217;s caused by code I put on the site <em>to work around other IE deficiencies<\/em>.<\/p>\n\n<p>For those who care, the problem seems to be related to using ECMAScript to traverse and modify the DOM.  There are <a href=\"http:\/\/www.google.com\/search?q=%22internet+explorer+cannot+open%22+%22operation+aborted%22&amp;btnG=Google+Search\">vague references to this<\/a> all over the &#8216;net&#8211;the symptom is that IE will load a page, then pop up an error dialog reading <q>Internet Explorer cannot open the Internet site <samp>http:\/\/example.com<\/samp>.  Operation aborted.<\/q>&#8211;but nothing in the way of <ins datetime=\"2003-12-03T00:13:00-05:00\">official<\/ins> confirmation, or even acknowledgement, of the issue by Microsoft.<\/p>\n\n<p><ins datetime=\"2003-12-03T00:16:00-05:00\">There is something resembling unofficial confirmation in <a href=\"http:\/\/www.google.com\/search?q=cache:DMsbgPshFCsJ:msdn.microsoft.com\/library\/en-us\/dnwebteam\/html\/webteam10012001.asp%3FFRAME%3Dtrue+%22internet+explorer+cannot+open%22+%22operation+aborted%22&amp;hl=en&amp;ie=UTF-8\">a Microsoft Web Team Q&amp;A<\/a> from 2001:<\/ins><\/p>\n\n<blockquote><p><ins datetime=\"2003-12-03T00:16:00-05:00\">Although we don&#8217;t fully understand the reason behind the error you are seeing&#8230; calling setTimeout to force the document update to occur after the onreadystate event handler has exited resolves the problem. This behavior is probably because you are modifying the document from within the onreadystate event handler.<\/ins><\/p><\/blockquote><\/div><div class=\"syndication-links\"><\/div>","protected":false},"excerpt":{"rendered":"How bad is this: I finally tracked down a problem some IE users were having with sirens3.com, and discovered that it&#8217;s caused by code I put on the site to work around other IE deficiencies. For those who care, the problem seems to be related to using ECMAScript to traverse and modify the DOM. There&hellip;","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"mf2_syndication":[],"venue_id":0},"categories":[3],"tags":[],"kind":false,"_links":{"self":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts\/306"}],"collection":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/comments?post=306"}],"version-history":[{"count":0,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/posts\/306\/revisions"}],"wp:attachment":[{"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/media?parent=306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/categories?post=306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/peterjanes.ca\/blog\/wp-json\/wp\/v2\/tags?post=306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}