Brad, that's because I closed the h1 tag again.
Some browsers (the better ones) auto-fix lousy HTML, and thankfully so, but for those of us checking in from hotels in Milpitas (or, I guess, from their offices in Ho-Ho-Kus), the browser options are more limited, and the problems are apparent.
The problem actually originated in Marshall's post; I fixed it, but then when Don replied to Marshall and quoted that post, he reintroduced the error. And the error comes because the quote function automatically introduces a pair of h1 tags before the quoted text; if someone erases one but not the other as they're editing quoted text, the fonts get screwed up. They serve no function, and should probably be eliminated in the quoting template...which would be a job for the politburo.
Some browsers (the better ones) auto-fix lousy HTML, and thankfully so, but for those of us checking in from hotels in Milpitas (or, I guess, from their offices in Ho-Ho-Kus), the browser options are more limited, and the problems are apparent.
The problem actually originated in Marshall's post; I fixed it, but then when Don replied to Marshall and quoted that post, he reintroduced the error. And the error comes because the quote function automatically introduces a pair of h1 tags before the quoted text; if someone erases one but not the other as they're editing quoted text, the fonts get screwed up. They serve no function, and should probably be eliminated in the quoting template...which would be a job for the politburo.