Outlook Rendering Question

@kenmckown ,

Outlook supports fairly limited HTML.  It's very frustrating.  You need to become familiar with VML if you want to become expert at email template coding (not just Marketo, this is universal).

For buttons, check out this resource, there is good reading here.

https://www.litmus.com/blog/a-guide-to-bulletproof-buttons-in-email-design.

Regards

Jo

Don't let the Outlook get ya down -- it's been a pretty normal thing to just "accept" that rounded corners aren't going to display in a "bulletproof" way for the last decade or so. For sure there's ways to get the initial render to be more reliable but the limitations it imposes in terms of the effort and edit-ability of the buttons makes it less reasonable in terms of effort-to-result (in my experience anyway).  Those "bulletproof" buttons have been a thing for just as long and I've yet in a decade to meet button code that is actually bulletproof, but it is some good buzzword marketing lingo I'll have to admit. In almost every case, these types of approaches will fail when email is forwarded (and that's the case for most buttons in any case) but the additional complexity you'll need to add and then manage and troubleshoot down the line is a much harder pill to swallow than having the buttons display un-rounded in some inboxes. 

Until Microsoft decides to join the rest of the world in doing things in a modern way, I think this'll just have to be something to deal with -- and I don't see them coming any more to their senses than they have in past where they'll push out updates that kinda work in some places and then still don't in others. 

If you really stop to think about this from an end-user perspective, folks that use things like Outlook on the daily which don't support rounded buttons are used to not seeing rounded buttons anyway. This is usually something the brand police are keen to try and enforce in email and generally means there's some disconnect between the builder of the brand and the understanding of the email design ecosystem.

Try using this code @kenmckown