Two good articles explaining the why's and wherefore's of the HTML Button element. When to use it, when not to use it, and how to avoid using the wrong elements with your JS click events.
I ran into (yet another) annoying Outlook 2016/2013 bug today. I had an image inside a table. I had the table aligned left. When reviewing in Outlook 2016/2013, the table containing the image was clipping over the text that was wrapping around it. Essentially, it was coving up the first letter of each word that was immediately to the left of the table. Luckily, I was able to find the fix on Campaign Monitor's blog.
Alas and alack, MS Outlook 2016 continues the trend of of being awful at rendering CSS and HTML for emails. Here are some great tips for coding to (or around) 2016's particular set of rendering bugs
Anyone who has had the "pleasure" of designing email has probably come to one very poignant conclusion: MS Outlook is terrible at rendering CSS and HTML for emails. The reason for this is that, starting with Outlook 2007, Microsoft thought it would be a reall great idea to stop rendering HTML email with the Internet Explorer engine, and instead render it with the MS Word rendering engine. Yes, you read that correctly: Word handles HTML and CSS for any emails in Outlook.
Came across this great cheat sheet listing many of the special HTML characters (or glyphs) we, as web developers, come across from time to time. In addition to listing the the HTML code, the chart also lists the numeric code; a description of the character; the HEX code; the ISO in CSS content (for use with pseudo-selectors like :before and :after); and the Octal (I'll be honest, I've never had to use this one before). All in all, a super-handy reference sheet to have around.
Gotta love those folks over at Smashing Magazine. I've been pretty happy with and loyal to Dreamweaver throughout my career. Lately, though, I've been doing more telecommuting, and Dreamweaver CS5.5 seems to have real problems with managing sites over a laggy network. Every time I'd try and make a change to the code or save a file, and application would come to a screeching hault for anywhere from 5 seconds to a full minute. Absolute death to productivity and morale.