I'm curious why Method 1 has better compatibility than Method 2, when with Method 2 you can use valign and have vertical borders that grow with the height of the TDs, unlike with Method 1 where you can't. With Method 2, you also don't have problems with one column dropping down in Outlook 2007+ like you do with Method 1. From my testing, Method 2 works just as well (if not better depending on the situation) as Method 1.

ETA: Thinking about this further, Method 1 has the capability of allowing us to control which column comes first in the stacking order on mobile (either the left or right col can be on top), whereas with Method 2, the left col or TD will always be on top on mobile.

Adding dir=rtl to the table will reverse the order of the columns, when there are multiple columns being displayed in a row. When it breaks down to a single-column layout, I believe it will display the columns in the order they appear in the code, so you do still have control in the order you want your content to be displayed.

However, some newer Android devices not supporting the display block method made the decision for me. I really like using the 2nd method, but there's too many devices and clients that aren't supporting it.

Yes, this Android thing is quite a pain - I've always used Method 1, but when I found out about Method 2 I was pretty stoked until I came across the issue in the other thread. Pretty much makes Method 2 useless unless there is a workaround, but I haven't found anything.

About method2: The "td { disaply: block }" doesn't work on Chrome in quircks mode. So people viewing the email in a webmail that stripe the doctype using Chrome and having a narrow screen won't see the "responsivity". You can't see that in litmus, but I found it happening on a couple of webmails here in italy.

You can test this by removing the doctyper and opening the email in Chrome and then narrow your screen.