Community Forum

Over the years we have built up a community of email marketers, coders and designers that live and breathe email.

Use the Email on Acid Forum like your virtual water cooler: Stop by to discuss email code, quirky clients and fixes and post your issues (with an example of the code) for our community to offer its assistance.

acidadmin

Administrator

One of the benefits of our test results is that we highlight exactly which lines of code are not supported by each email client. If we didn’t highlight it, you wouldn’t know that it wasn’t supported.

I think the term “error” is what is throwing you off. Even though you may find “errors,” as long as you are happy with the way your design is rendering, there is no cause for concern. Maybe we should consider redefining unsupported code as “discrepancies.”

From a programming standpoint however, there is no way for us to know what an end user feels is an acceptable vs an unacceptable discrepancy.

Are you concerned that if you show this acid test to a customer, they might think there are several errors? One feature we hope to build soon is the ability to forward the test result to a friend or customer for approval. In that scenario, we would not include the code analysis.

Thanks so much for the feedback and the open dialog!

smarsh

Newbie

I guess the term “error” was concerning me a bit. I realize that some e-mail clients are better at rendering than others, but just wanted to be sure that I’m not naive in thinking if it looks good, it’s fine. Thanks for the clarification.

Am I right to believe that once you go beyond very basic HTML e-mail, one or another e-mail client will “dislike” something used to achieve the layout, or is it possible to have a more elaborate layout and make evryone happy?

Right now I’m not concerned with showing someone else - it’s an internal newsletter I’m working on. In the future, that would be a nice feature.