Showing posts with label Internet Explorer. Show all posts
Showing posts with label Internet Explorer. Show all posts
Thursday, January 1, 2009
IE6 freeze with MOSS 2007
emposha wrote about how to handle a situtation where IE6 chokes on MOSS preview pages.
Wednesday, September 10, 2008
Internet Explorer does not support http vary header
It was always assumed, but I just saw this quote from Microsoft:
Internet Explorer does not fully implement the VARY header per Requests for Comments (RFC) 2616. The Internet Explorer implementation of VARY is that it does not cache any data except for Vary-Useragent
Tuesday, September 9, 2008
Internet explorer cannot open the internet site: operation aborted
During an integration with a third party provider we were unfortunate enough to get the error
After a long and hard effort by this provider they pointed out that while the view-source indeed looked like the script is just before
As it turns out there was some code on the page that wrote an unclosed
I found out that the broken pages used some JQuery plugins (tooltips, jqmodal, etc.) to produce fancy decorations and effects. These scripts attached to
They funny (or maybe sad) thing was that on Firefox we did not get any error but the page simply disappeared. Chrome worked just fine.
Internet explorer cannot open the internet site http://localhost: operation abortedYes, we have read http://support.microsoft.com/kb/927917 and did move the 3rd-party's script to be just before the
</BODY> tag but to no avail.After a long and hard effort by this provider they pointed out that while the view-source indeed looked like the script is just before
</BODY> when looking at the DOM itself (they used Dominspector, I used the IE Developer Toolbar) it showed that the script was inside a <DIV> element.As it turns out there was some code on the page that wrote an unclosed
<DIV>. This made IE "fill in the blanks" and guess (wrongly) where it should place the closing </DIV> Fixing this javascript made the error go away on most pages. But not all.I found out that the broken pages used some JQuery plugins (tooltips, jqmodal, etc.) to produce fancy decorations and effects. These scripts attached to
$document.ready and did $('body').appendTo(...). This effectively added a couple of items to the DOM between the 3rd-party script and the </BODY>. I am still not quite sure why this should cause IE to choke but since we have a tight schedule we simply changed those scripts to add their stuff to some other elements. This indeed solved out problem.They funny (or maybe sad) thing was that on Firefox we did not get any error but the page simply disappeared. Chrome worked just fine.
Tuesday, August 26, 2008
Misplaced elements with position:relative
We had a situation where we had three <DIV> elements in a column and the middle element had content dynamically loaded into it after the page has completed loading. When the middle element finished loading, some of the content of the last element seemed to forget its parenthood and floated nicely over the second element.
Naturally this only happened in Internet Explorer (what else).
After a lot of digging we noticed that the misplaced content of <DIV>#3 had a
Luckily I chanced upon an article by Holly Bergevin et al. called On having layout which was enlightening. Understanding that IE will only respect the element's state if it have the
In our specific case I used
Tip: you can use IE Developer Toolbar to check if an element hasLayout. It will show the
Further credit is due to Ingo Chao who wrote relatively positioned parent and floated child – disappearance.
Naturally this only happened in Internet Explorer (what else).
After a lot of digging we noticed that the misplaced content of <DIV>#3 had a
position:relative style (indicated as #4 in the image above). It is "well known" that IE does not handle relative positioning properly when the layout of the page change. Luckily I chanced upon an article by Holly Bergevin et al. called On having layout which was enlightening. Understanding that IE will only respect the element's state if it have the
hasLayout property quickly solved the problem.In our specific case I used
display:inline-block to force <DIV>#3 to have hasLayout set to true, which made IE respect the element's style and re-render the element's content (i.e. <DIV>#4) after re-positioning it. My only concern now is what effect this might have on rendering performance, but it will have to do for now.Tip: you can use IE Developer Toolbar to check if an element hasLayout. It will show the
hasLayout property as set to -1 if hasLayout is true.Further credit is due to Ingo Chao who wrote relatively positioned parent and floated child – disappearance.
Thursday, January 3, 2008
document.body.scrollTop in IE
It seems that
See more at document.body.scrollTop in IE
document.body.scrollTop does not work in IE6 if the document's doctype is defined as <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">(document.documentElement.scrollTop?document.documentElement.scrollTop:document.body.scrollTop)See more at document.body.scrollTop in IE
Thursday, September 6, 2007
Avoding browser history when changing iframe src
We ran into a problem where we needed to have an iframe who's source needed to be changed dynamically by a javascript based on some user data. The issue was that Internet Explorer saved the iframe's old url in the history. The simple solution is to dynamically write the iframe with it's real src instead of having an iframe on the page and then changing it's src.
You do it like this:
Elementry, my dear Watson.
You do it like this:
var iframeHeaderCell = document.getElementById('wheretoputheiframe');
var dynamicURL = 'http://...' //your url
var iframeHeader = document.createElement('IFRAME');
iframeHeader.id = 'iframeHeader';
iframeHeader.src = dynamicURL ;
iframeHeader.width = ...;
iframeHeader.height = ...;
iframeHeader.scrolling = 'no';
iframeHeader.frameBorder = 0;
iframeHeader.align = 'center';
iframeHeader.valign='top'
iframeHeader.marginwidth = 0;
iframeHeader.marginheight = 0;
iframeHeader.hspace = 0;
iframeHeader.vspace = 0;
iframeHeaderCell.appendChild(iframeHeader);
Elementry, my dear Watson.
Subscribe to:
Posts (Atom)