In article <bm**********@sparta.btinternet.com>,
John Robin Devany <fi*******@lastname.com> wrote:
JP. Baker wrote:
This is the 3px jog bug.
http://www.positioniseverything.net/...reepxtest.html
Indeed it is, thanks for the link.
I have gained great familiarity with it over the last fortnight.
November 2002. Implemented 'transitional' design for university site.
(table top and bottom for backward compatibility, div navigation and
content). Noticed occasional misplaced bullets in lists put it down
to IE error with custom bullets. Most pages were placeholders at the
time so were shorter than navigation.
Christmas 2002-March 2003. Broke my ankle. My boss seemed more concerned
at the jog problem than my health. Of course there was real content now.
April 2003. went live with site, deciding that a few pixels were IE's
problem and we would have to lump it.
June 2003-October 2003. Released template to other departments. Some of
whom had pages that were just tables (AAAAARGH).
October 2003. Identified as 3px jog (float) bug. Tried to find any fix
that wouldn't cause a regression. (Unfortunately we have a footer so
can't just go to 'position: absolute'. Cosmetic patch, temporarily put
in on Monday, equivalent of:
<!--[if IE 6]>
<style type="text/css">
#navigation {display: expression('absolute')}
#footer {padding-top: expression(Math.max(navigation.offsetHeight-
content.offsetHeight, 0))}
@media print {#footer {padding-top: 0 !important}}
</style>
<![endif]-->
Which needs JScript and, due to another bug, doesn't get saved to disc.
(at least the other browsers only see a comment)
Now. No idea how to redeem the situation.
[ links off
http://www.bris.ac.uk/ ]
nhoJ
--
John P Baker