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!
