IE has always had a bunch of bugs with its floats. I know that some of them involve interactions with :hover. It's a long shot but you might try removing the a:hover style for your links.
It's unusual to float the main content of a page. Why not try floating the sidebar instead? It might just evade the bug that the current layout is triggering.
It's a long shot but you might try removing the a:hover style for your links.
Thanks, I'll certainly try that.
Why not try floating the sidebar instead?
ummm well I'm sure there was a reason... :-)
I can't remember now if it was something to do with how I wanted the page to look - I know I didn't want the content to wrap around beneath the sidebar after the sidebar finishes - but it might just have been someone's recommendation for SEO, because of (alleged) higher weighting for terms towards the top of the page.
It might just evade the bug that the current layout is triggering.
True, and I guess I'll have to do that if it works and if I can't fix it another way. Doubt if I'll get to that in the next few days though... have put up a workaround note for now.
I know I didn't want the content to wrap around beneath the sidebar after the sidebar finishes
That's easy to avoid by putting the content in a div whose left margin is wider than the sidebar. It can still be a %age of page width (the margin, as well as the columns). I think IE7 even honours min-width, though earlier versions of IE certainly don't.
(alleged) higher weighting for terms towards the top of the page
I don't think your sidebar has enough content to make it worth worrying about such factors, if they even exist.
Well deleting the a:hover CSS has made it so the link from the title of the first article takes you to the article page. Which is a step in the right direction however illogical :-)
I notice I feel very reluctant to reorganise my pages any further just to humour IE7! I think before resorting to that, I might try a few of the hasLayout workarounds where you put in an extra bit of CSS which doesn't really do anything. ... when I have time & headspace for that.
Another thing about having the content first is it means on a slow connection it appears first, which (though again non-crucial) is desirable behaviour I think.
Comments 4
It's unusual to float the main content of a page. Why not try floating the sidebar instead? It might just evade the bug that the current layout is triggering.
Reply
Thanks, I'll certainly try that.
Why not try floating the sidebar instead?
ummm well I'm sure there was a reason... :-)
I can't remember now if it was something to do with how I wanted the page to look - I know I didn't want the content to wrap around beneath the sidebar after the sidebar finishes - but it might just have been someone's recommendation for SEO, because of (alleged) higher weighting for terms towards the top of the page.
It might just evade the bug that the current layout is triggering.
True, and I guess I'll have to do that if it works and if I can't fix it another way. Doubt if I'll get to that in the next few days though... have put up a workaround note for now.
Thanks!
Reply
That's easy to avoid by putting the content in a div whose left margin is wider than the sidebar. It can still be a %age of page width (the margin, as well as the columns). I think IE7 even honours min-width, though earlier versions of IE certainly don't.
(alleged) higher weighting for terms towards the top of the page
I don't think your sidebar has enough content to make it worth worrying about such factors, if they even exist.
Reply
I notice I feel very reluctant to reorganise my pages any further just to humour IE7! I think before resorting to that, I might try a few of the hasLayout workarounds where you put in an extra bit of CSS which doesn't really do anything. ... when I have time & headspace for that.
Another thing about having the content first is it means on a slow connection it appears first, which (though again non-crucial) is desirable behaviour I think.
Thanks again for your expertise...
Reply
Leave a comment