HTML 5 attribute support needed for responsive tables to work

HTML 5 attribute support needed for responsive tables to work

I created a responsive data table for an email campaign in Design Studio. For this to work, the table uses the data-title attribute. Upon save and close, when I go back in the attribute is stripped out. We need the attribute to remain intact all the way through deployment, or the data table is meaningless in the responsive mobile design.

Example: <tr>
<td data-title="#1 Viewed">most viewed 1</td>
<td>&nbsp;</td>
<td data-title="#1 Post">most popular 1</td>
</tr>


Marketo needs to support HTML5 attributes for responsive tables to work! This is also important for accessibility. Let's make it happen, please!
8 Comments
Justin_Cooperm2
Level 10
Did you use Email Actions > HTML Tools > Replace HTML to paste your code in? 
Anonymous
Not applicable
Hi Justin,

No, didn't know that would prevent the editor from stripping. Will try that and report back. Thanks!
Amy_Lepre
Level 7
That would negate using an email template, though, wouldn't it? That is unfortunate. It would be great to be able to use HTML5 and also use email templates.
 
Justin_Cooperm2
Level 10
@Amy - You can put his example in an email template as well. It will work if you either paste that code into a template or use the workflow I mention above. It will not work if you click the HTML button in the TinyMCE rich text editor as that will strip it out.


Anonymous
Not applicable
Thanks, Justin - that works! Is there anything to worry about with the "...will disconnect from template..." notice?
Justin_Cooperm2
Level 10
Hi Arlene - You have two options:

1. Put the code into the template itself. Thing about this is that all new emails created off of that template will have those elements pre-loaded. 

2. Choose "Replace HTML," which will allow you to edit the code for an individual email. It will disconnect it from the template, which is not problematic, as long as you don't break other things that are in your template by adding things!
Anonymous
Not applicable
HI Justin,

I tried #1, but that doesn't work for our needs because that content will be changing with each newsletter. #2 does work. Question, about breaking things ... where should I "not" add things or what things shouldn't I add?

My template is essentially this: one single giant editable region around all of the guts. Multiple editable regions breaks my responsive design. This was the only way I could build a template that our CRM folks could populate, so we don't have to do the 1:1 template to email. Is it OK to add things inside this editable region, or do you mean don't add other "template" sections/editable regions?

Sorry to get off topic here, but the word "break" freaks me out (lol). Thanks!
kh-lschutte
Community Manager
Status changed to: Already have it