And there are quite a few of those on that page

IWETHEY v. 0.3.0 | TODO

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

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.

Hmmm . . . this is interesting: Safari and Chrome . . . - (Andrew Grygus) - (40) - Sept. 26, 2010, 10:35:33 PM EDT

What's really interesting... - (malraux) - (11) - Sept. 26, 2010, 11:00:10 PM EDT

Thanks, I'll give that a try . . . - (Andrew Grygus) - (3) - Sept. 26, 2010, 11:23:22 PM EDT

Different Scott... ;-) - (malraux) - (2) - Sept. 26, 2010, 11:30:19 PM EDT

Were you using a Mac? -NT - (Andrew Grygus) - (1) - Sept. 26, 2010, 11:49:05 PM EDT

Yes. -NT - (malraux) - Sept. 27, 2010, 09:18:43 AM EDT

Timing issues, huh? - (Andrew Grygus) - (6) - Sept. 27, 2010, 01:21:47 AM EDT

Not just speed - (drook) - (5) - Sept. 27, 2010, 09:54:09 AM EDT

And there are quite a few of those on that page - (scoenye) - (4) - Sept. 28, 2010, 07:09:26 PM EDT

I've been over and over my nesting and closings . . . - (Andrew Grygus) - (3) - Sept. 28, 2010, 09:36:45 PM EDT

Try the validator - (drook) - (2) - Sept. 28, 2010, 10:42:48 PM EDT

Not so much unbalanced nesting - (scoenye) - Sept. 28, 2010, 11:01:52 PM EDT

Yeah, a lot of values are not quoted . . . - (Andrew Grygus) - Sept. 29, 2010, 01:12:03 AM EDT

Typo - "North American. buyers" -NT - (Another Scott) - Sept. 26, 2010, 11:00:55 PM EDT

Conclusion: Safari (Win) can't render W3C validated code. - (Andrew Grygus) - (26) - Oct. 3, 2010, 02:47:06 AM EDT

Interesting.. - (Ashton) - Oct. 3, 2010, 04:07:02 AM EDT

Re: Conclusion: Safari (Win) can't render W3C validated code - (mvitale) - Oct. 3, 2010, 09:28:09 AM EDT

Still shifted. - (malraux) - (7) - Oct. 3, 2010, 11:16:55 AM EDT

I was thinking that last as well. Must be something subtle. -NT - (Another Scott) - Oct. 3, 2010, 11:22:14 AM EDT

I have done the div thing mvitale suggested. - (Andrew Grygus) - (5) - Oct. 3, 2010, 11:57:49 AM EDT

Quick thought: Possible font substitutions? - (Another Scott) - (1) - Oct. 3, 2010, 12:04:06 PM EDT

Re: Quick thought: Possible font substitutions? - (Andrew Grygus) - Oct. 3, 2010, 12:11:04 PM EDT

Works. - (malraux) - (2) - Oct. 3, 2010, 12:10:51 PM EDT

It doesn't work for the other formatting problems though. - (Andrew Grygus) - (1) - Oct. 3, 2010, 12:34:07 PM EDT

Not a fix, a replacement. -NT - (malraux) - Oct. 3, 2010, 12:52:05 PM EDT

weird issues - (SpiceWare) - (8) - Oct. 3, 2010, 01:49:16 PM EDT

Somebody updated it - (SpiceWare) - (7) - Oct. 5, 2010, 11:19:55 AM EDT

Yup, and a "reduced test case" . . . - (Andrew Grygus) - (6) - Oct. 5, 2010, 12:05:46 PM EDT

Well, if you can't fix the problem, fix the spec :-( -NT - (hnick) - Oct. 5, 2010, 02:10:47 PM EDT

I can try to reduce it - (SpiceWare) - (4) - Oct. 5, 2010, 02:47:41 PM EDT

Oh, I can reduce it very easily, but . . . - (Andrew Grygus) - (3) - Oct. 5, 2010, 04:58:43 PM EDT

And here it is. - (Andrew Grygus) - (2) - Oct. 5, 2010, 11:11:07 PM EDT

On a Mac - (Ashton) - Oct. 6, 2010, 02:09:06 AM EDT

Display at 1149 pixels wide... - (folkert) - Oct. 6, 2010, 07:34:39 AM EDT

Just thought of something - (drook) - (5) - Oct. 3, 2010, 09:26:25 PM EDT

Yep. - (malraux) - Oct. 3, 2010, 10:50:07 PM EDT

Standard but deprecated - (scoenye) - Oct. 3, 2010, 11:08:00 PM EDT

I have specified doctype 4.1 transitional . . . - (Andrew Grygus) - (2) - Oct. 4, 2010, 12:21:46 AM EDT

One way to consistently clear it... - (scoenye) - (1) - Oct. 4, 2010, 10:41:59 PM EDT

Re: "One way to consistently clear it... - (Andrew Grygus) - Oct. 4, 2010, 11:54:05 PM EDT

"Web Browser v2.30.2" or Epiphany... - (folkert) - Oct. 3, 2010, 10:45:51 PM EDT

Hitotsu, futatsu, mittsu, yottsu.
60 ms