August 09, 2005
Safari/Mac Rendering Woes
Something is messing up this page on Safari, and (not having a Mac to test with) I can’t figure out what on earth it could be.
The problem pre-dates the addition of the clustermap in the right margin (which will start functioning tomorrow, if all goes well). As far as I can tell, it also seems to be unrelated to the previous change, the addition of the Google page rank graphic in the right margin. I’ve seen a screenshoot and both of the outside columns are overlapping the center one, leaving a wide swath of blank stuff where the two outside columns should be.
I know that my HTML isn’t completely standards compliant; some day I’ll move to wordpress and do a better job. In the meanwhile, if anyone has a suggestion as to what might be the cause of this problem, I would be grateful for advice.
Posted by Michael : August 9, 2005 11:30 AM | Discourse.net | TechnoLinks
Slashdot
It!
You can run your site through http://validator.w3.org/ to get a readout on some HTML errors.
Based on the readout, I wonder if changing this line:
<link REL="SHORTCUT ICON" HREF="http://www.discourse.net/tie2.ico">
to
<link rel="SHORTCUT ICON" href="http://www.discourse.net/tie2.ico" />
will solve the problem.
It's a small thing, but some browsers are better at "fixing" non-validating code when they render the file. Safari might be hiccuping on that piece of mal-formed HTML and then breaking the rest of the page.
Posted by: Cathy at August 9, 2005 03:31 PMOh this is weird. The template for my homepage -- which you never see since it gets 'improved by IE' has the line
< link rel="SHORTCUT ICON" href="http://www.discourse.net/tie2.ico" / >
the same line is visible in my index.html file when I look at it in a text editor.
And, if you view the source in IE, you see it as written above.
But -- if you view the source in Firefox, the final / is missing. No idea why Firefox ate it.
So I don't think that's the source of my problem.
OTOH, the good news is that people with Macs viewing the site at 1024 or greater report no problems. I'm unsure if I've cured it at 800x600 or 640 x 480. Being a Mac ignoramus, I don't even know if Macs run at those resolutions!)
Posted by: michael at August 9, 2005 03:55 PMI can only speak for my own use but I don't SEEM to be having any problem viewing your page on Safari, on any of my Macs. They are all flat-screen monitors.
Hope you figure it out, for the sake of interested readers, regardless of their hardware choice.
phil ford
mpls, mn
I wonder if there's a browser sniffing script that serves up a different page for different browsers? And one version doesn't have that line?
Or maybe there is some conflict with the stylesheet in setting up the layout of all the <div></div>s? And when it gets stretched out the conflict appears to go away? (Of course, if this is the case it could just as easily be a browser rendering engine error as a coding error.)
Of course it's hard for me to know for sure, not being able to see the patient (I don't have Safari either).
But it's always fun to comment on other people's sites and pretend I know what's going on :-)
Or maybe it's the other thingimabobbie.
Posted by: BroD at August 9, 2005 08:08 PMFine on my powerbook G4, running Safari on 10.4.
Posted by: hilzoy at August 10, 2005 01:31 AMI hear that it's fixed. I wish I knew how or why....
Posted by: Michael at August 10, 2005 08:07 AM