You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain components (like mjml-section or mjml-button) generate Margin styles with an uppercase M.
This was useful historically for Outlook.com where CSS support depended on case. So margin:0 would get stripped by Outlook.com, but not Margin:0;. This is no longer the case (no pun intended) since the last versions of Outlook.com so it can be safely changed back to lowercase margin everywhere. This might be a small thing but it can be one less quirk to figure out for newcomers and make MJML look more up to date towards modern best practices.
Some companies have clients working on older systems. Having backwards compatibility is a good thing in my opinion. Outlook has the capability to parse between the two.
Are you sure about that? My understanding was that every Outlook.com accounts were migrated to the new Office 365 type of accounts. Also there’s been two successive versions of Outlook.com where this bug has no longer been there.
Certain components (like mjml-section or mjml-button) generate
Margin
styles with an uppercaseM
.This was useful historically for Outlook.com where CSS support depended on case. So
margin:0
would get stripped by Outlook.com, but notMargin:0;
. This is no longer the case (no pun intended) since the last versions of Outlook.com so it can be safely changed back to lowercasemargin
everywhere. This might be a small thing but it can be one less quirk to figure out for newcomers and make MJML look more up to date towards modern best practices.See this bug report for more details.
The text was updated successfully, but these errors were encountered: