Comments on: Strange IE Bug http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/ ShafTek.org = SHAFranovich TECHnologies Sun, 05 Feb 2012 15:43:17 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Anonymous http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/comment-page-1/#comment-99 Anonymous Fri, 14 Jan 2005 22:15:39 +0000 http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/#comment-99 this workds very well explained. this workds very well explained.

]]> By: homer http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/comment-page-1/#comment-98 homer Thu, 13 Jan 2005 20:04:18 +0000 http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/#comment-98 calling the javascript within a settimeout call worked for me. calling the javascript within a settimeout call worked for me.

]]> By: netwizard http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/comment-page-1/#comment-97 netwizard Tue, 11 Jan 2005 19:33:49 +0000 http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/#comment-97 What about using setTimeout like suggested by the MSDN team? What about using setTimeout like suggested by the MSDN team?

]]> By: Peter J. http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/comment-page-1/#comment-96 Peter J. Tue, 11 Jan 2005 19:24:08 +0000 http://www.shaftek.org/blog/2005/01/11/strange-ie-bug/#comment-96 If only it were that simple... but I don't use <script> anywhere but in the <head> on the Sirens site. Wound up just removing the offending code, which seems to be the safest thing since it appears to be a timing issue. If only it were that simple… but I don’t use <script> anywhere but in the <head> on the Sirens site. Wound up just removing the offending code, which seems to be the safest thing since it appears to be a timing issue.

]]>