Issue Information
-
#000029
-
Issue
Issue Confirmations
-
Yes (2)No (6)
White line above QuickNav in IE9
http://api.browsersh...95613708735.png
I'd personally just scrap the whole design, make a new page layout using the latest HTML and CSS standards, not necessarily HTML5 and CSS3.
-Gata
I believe it's how IE renders the code that causes it. I seem to recall this particular main page might have been coded at a time when Netscape was still alive.
I'd personally just scrap the whole design, make a new page layout using the latest HTML and CSS standards, not necessarily HTML5 and CSS3.
It's actually not an IE glitch, those elements do exist on the page and should be rendered. They are actually invaid image elements. Take for example the line above the QuickNave:
<img width="147" height="1" alt="" spacer="/newimg/spacer.gif">
It's an invalid image tag (I think "spacer" is a typo of "src"). The reason it's only visible in IE is because IE shows a placeholder where images fail to load where other browsers colapse them.
Simply removing these tags would work as a quick fix but the whole page could use a rewrite, it's very badly formed and has no Doctype.
Also, that's not IE9 in the screenshot, it's the Desktop version of IE10 for Windows 8 though it appears relatively the same in IE7-IE10.
I agree the front page probably needs to be redone, but that's a pretty giant undertaking.
I can definitely understand why it's be such a big undertaking... Though, if someone had the knowledge and time to do that, then it might be something to eventually look into. That said, it'd also partly depend on if that person knew much about HTML 5 or not, since that'd be probably what would be used. And it'd be very likely the person would need to be on staff, ruling out volunteers, correct?
All you would need to do is replace all of the tags like this:That certainly is a problem... I had thought it was there for me too at first, but it turns out I was looking in the wrong spot. >>' But there isn't anything there in Firefox, which is the problem... It's harder to troubleshoot, when only one browser is confirmed to be the issue.
I can definitely understand why it's be such a big undertaking... Though, if someone had the knowledge and time to do that, then it might be something to eventually look into. That said, it'd also partly depend on if that person knew much about HTML 5 or not, since that'd be probably what would be used. And it'd be very likely the person would need to be on staff, ruling out volunteers, correct?
<img width="147" height="1" alt="" spacer="/newimg/spacer.gif">With code like this this:
<img width="147" height="1" alt="" src="/newimg/spacer.gif">Or, better yet, remove them entirely and stop making pointless requests to the server for invisible images.
Also, HTML 5 is just a simplified version of XHTML. It's actually easier than the old HTML standards.
I haven't actually looked into it much, to be honest... I've heard it's rather simple, but I haven't gone to look at it much, though I should.
1 user(s) are reading this issue
0 members, 1 guests, 0 anonymous users










