We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running the following example with the latest version of MRML the mj-class elements seem to be ignored https://github.com/jdrouet/mrml/blob/main/resources/compare/success/mj-attributes.mjml
mj-class
I was attempting to upgrade from v0.3.0 to v1.2.2 when I noticed the issue.
<mjml> <mj-head> <mj-attributes> <mj-text padding="0" /> <mj-class name="blue" color="blue" /> <mj-class name="big" font-size="20px" /> <mj-all font-family="Arial" /> </mj-attributes> </mj-head> <mj-body> <mj-section> <mj-column> <mj-text mj-class="blue big"> Hello World! </mj-text> </mj-column> </mj-section> </mj-body> </mjml>
Expected Result
<td align="left" style="font-size:0px;padding:0;word-break:break-word;"> <div style="font-family:Arial;font-size:20px;line-height:1;text-align:left;color:blue;">Hello World!</div> </td>
Actual Result
<td align="left" style="font-size:0px;padding:0;word-break:break-word;"> <div style="font-family:Arial;font-size:13px;line-height:1;text-align:left;color:#000000;">Hello World!</div> </td>
The text was updated successfully, but these errors were encountered:
@abstractcoder with [email protected] the bug is now fixed 😉
Thank you very much for the issue!
Sorry, something went wrong.
jdrouet
Successfully merging a pull request may close this issue.
When running the following example with the latest version of MRML the
mj-class
elements seem to be ignored https://github.com/jdrouet/mrml/blob/main/resources/compare/success/mj-attributes.mjmlI was attempting to upgrade from v0.3.0 to v1.2.2 when I noticed the issue.
Expected Result
Actual Result
The text was updated successfully, but these errors were encountered: