Like leaving a sentence with no punctuation, there is just something wrong about not identifying content with a p tag. It feels unnatural… even though it doesn’t really matter to an email client.
But, each email client renders that p tag a little differently. While most respect your formatting, other flip you the bird and I got tired of fighting with them. Even with stripping formatting down to it’s essence, if the design doesn’t accommodate for variable content height or flow then it simply looks broken. What to do what to do?
“ah-ha!” I say to myself. “What if there wasn’t a p tag at all?”And in marches SPAN to save the day!
The only time it would really matter is if the content is getting hung up on your website and how hard is it to do a find/replace for “span”. Finally, success!
I can’t tell you how much details like this bother me. I want the user experience to be consistent across all channels and it’s simply unacceptable to accept it as ‘good enough’. Perfection is priceless.
Now, I know what you’re going to say… “it’s a bloody html email” and “who gives a $#!&?” Well the answer to both those is, me. 🙂 And for all those templates you can get online for your emails with email client specific hacks in them, you still don’t get a consistent presentation across the board. The truth is you can’t approach it like you would a standard html project because it’s not. It’s a bloody email.