[error_key] => json.invalid.value.no_script_tags
[error_message] => #/email_content: Field does not support script content.
I found that the following style attributes threw the above error. Can these be added to the filter?
Thanks for the detailed report. We'll get those added ASAP, will post an update when we have a date for the updated release.
As an aside, we'll open up an item on our side to go through the current HTML 5/CSS 3 working spec and see which of the tags and attributes are in a stage where we can implement them into our filter. This is a bigger excercise obviously but we'll get this in our backlog so that we can be ready for developers who are using these new features.
As always, I like to put in a disclaimer that with new tags in HTML 5 and CSS 3 attribute. We highly recommend you test out your email designs in the clients and browsers you think your customers will read them in. Support for those tags and attributes can vary greatly by email client and browser and you never want to run into a problem where a great design ends up losing everything because of a compatability issue.
Any update on this? I work for an organization with strict graphic standards that include rounded corners on all images and many text blocks - this would be invaluable and might sell us on staying with Constant Contact.
We recently released an update to the API which should have resolved most, if not all, of the validation issues related to email content. At this time, we have an exact mirror of the UI validation. You can read more in our release notes here: http://techblog.constantcontact.com/api/release-updates/api-release-notes-december-2013/
If you are still seeing problems with any CSS, HTML or content, please open up a new thread with that specific problem. It's likely that there is either a bug at that point or we need to have an update done to our UI validation and will need to work with that team.