What's really interesting...

Post #333,178 by malraux 9/26/10 11:00:10 PM Reply	What's really interesting... If I save that page locally, Safari displays it fine. Chrome displays it improperly from both locations. Both browsers use WebKit, incidentally. Except, now Chrome is displaying it fine locally. Must be a timing issue. Try adding a div around the image, name, and description, and close it just before the br clear. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #333,181 by Andrew Grygus 9/26/10 11:23:22 PM Reply	Thanks, I'll give that a try . . . . . when I can get back to it. What I saw on the Mac was the top left photo and the whole body shifted to the right of the left column, which looked pretty bad. These failures to clear left aren't so bad. I'll have to take a look on another Mac as soon as I can. What! you only noticed one typo on that huge page? Fixed - thanks.
Post #333,182 by malraux 9/26/10 11:30:19 PM Reply	Different Scott... ;-) I didn't see the photo shifted, just everything below the second HR. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #333,183 by Andrew Grygus 9/26/10 11:49:05 PM Reply	Were you using a Mac?
Post #333,203 by malraux 9/27/10 9:18:43 AM Reply	Yes. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #333,185 by Andrew Grygus 9/27/10 1:21:47 AM Reply	Timing issues, huh? So these browsers achieve the high speed they boast of by simply not bothering to render anything they find inconvenient? Since I use nothing but the most basic html on my pages, this says a lot about their quality.
Post #333,210 by drook 9/27/10 9:54:09 AM Reply	Not just speed That's been part of HTML rendering since just about always. Anything a browser doesn't recognize it will ignore. Improperly nested or closed elements are essentially arbitrary. I've seen arguments saying the only way to "fix the web" is for browsers to always render strict. Of course the other side chants "strict in what you emit, liberal in what you accept". -- Drew
Post #333,317 by scoenye 9/28/10 7:09:26 PM Reply	And there are quite a few of those on that page "Improperly nested or closed elements" that is... (and even a few freshly minted ones.) There is a good chance that Safari and Chrome are indeed reacting differently to the coding errors.
Post #333,321 by Andrew Grygus 9/28/10 9:36:45 PM Reply	I've been over and over my nesting and closings . . . . . and I'm very careful with closings, applying them even thought browsers traditionally correct for them being missing. Now get this. If I move the edge of the browser window in a ways all the formatting becomes correct. If I move the edge back out, some of the fixed errors stay corrected and others revert to incorrect. I will inspect my nesting and closings one more time, but don't expect to find anything.
Post #333,325 by drook 9/28/10 10:42:48 PM Reply	Try the validator http://validator.w3.org/ Looks like your biggest problem is not quoting values. -- Drew
Post #333,328 by scoenye 9/28/10 11:01:52 PM Reply	Not so much unbalanced nesting but disallowed nesting. E.g. there are a lot of anchor constructs that contain an H2. That is block level content where only inline is allowed. (And there are also three instances where the A when missing, resulting in a NAME element). None of the warnings occur on one of the images you're floating, but as these are also embedded in anchors, it is possible that an imbalanced anchor tag causes the BR to happen at an unexpected spot.
Post #333,335 by Andrew Grygus 9/29/10 1:12:03 AM Reply	Yeah, a lot of values are not quoted . . . . . because the originals of a lot of my stuff were done before the XML spec came out requiring the quotes and they got replicated. HTML didn't require them. I've been inserting them as I go, but there's a hell of a lot of them - and I'm not using XML.

Welcome to IWETHEY!