> On Aug 12, 11:42 pm, cass-hacks wrote:

> > How long and how many times have you been harping on this?

> > I know of two ways you can fix it, assuming Google likely won't, 1.
> > disallow cache, 2. stick this in the head of your pages,
> > <!--[IF  IE]>
> > <script type="text/javascript">
> > if (window.attachEvent) {
> >   window.attachEvent('onload',check_cached);}

> > function check_cached () {
> >   var divs = document.getElementsByTagName('div');
> >   for (var x=0; x<divs.length; x++) {
> >     if ( divs[x].style.position == "relative") {
> >       var store = divs[x].innerHTML;
> >       divs[x].parentNode.innerHTML = parent.innerHTML +
> > divs[x].innerHTML;
> >     }
> >   }}

> > </script>
> > <![endif]-->

> > What that does is first test to see if the browser is IE using
> > conditional comments, which is the only browser that has a problem,
> > then it creates a collection of divs and searches for the one that has
> > position:relative set inline, then it copies the innerHTML of that
> > div, which should be the only one on a page with all styles defined in
> > a external style sheet, and adds it to the innerHTML of the div's
> > parent.

> > Or, you can just put up with the broken cache display until and if
> > Google ever does something about it.

> > I'm surprised though that the entire site hasn't been dropped from the
> > index though considering that page doesn't validate.  :-()

> > tsk tsk tsk.  :-)

> > Craig

> > On Aug 13, 10:45 am, webado wrote:

> > > Craig, for PETE"S SAKE!

> > > What did I say?

> > > It's GOOGLES  open div, not mine!

> > > So Google must remove it.

> > > On Aug 12, 9:39 pm, cass-hacks wrote:

> > > > > It's not that IE screws up anything. It's that in this one case
> > > > > Firefox is more forgiving than IE,  that's all.

> > > > Or, it could be that Firefox, Opera, Safari, Konqueror, as well as all
> > > > the other Linux variants get it right and Internet Exploder gets it
> > > > wrong.

> > > > > Allow me to be totally peeved over this.

> > > > Why?  If you want to get peeved, get peeved at the right entity and
> > > > for the right reason.

> > > > Google is partly responsible for adding styling that is known to screw
> > > > up Internet Explorer but if IE worked the way it should, it wouldn't
> > > > be an issue.

> > > > > I know it will work if the stupid div is closed.

> > > > If one adds the closing </div> where browsers would assume one to be,
> > > > at the end, it still doesn't work.

> > > > Add a closing div just after the opening div, it then works but then
> > > > the point of the opening div, if there was one in the first place, is
> > > > lost.

> > > > As it is, with the closing of the div assumed by browsers to be at the
> > > > end of the document, the problem is that the div is setting
> > > > position:relative on the entire page which shouldn't be a problem for
> > > > a standards compliant browser.

> > > > Remove the style="position:relative" and whether or not you add the
> > > > closing div, the page will then display correctly in IE-6 and IE-7.

> > > > The best option would be to simply remove the opening div since it
> > > > basically achieves nothing except causing problems for IE, which even
> > > > a gentle breeze has been known to do.  :-()

> > > > Craig- Hide quoted text -

> > - Show quoted text -