-
Notifications
You must be signed in to change notification settings - Fork 966
New issue
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
Allow for lang
attribute in <mj-body>
#2355
Comments
AlternativeThe CommentsGood suggestion! And, taking nothing away from it ... This option is appropriate if no user would want, for example, This option abstracts a little complexity from MJML users, an added value for MJML. This option makes MJML more maintainable because the team is less likely to get questions about the difference between the two attributes. This option keeps MJML more consistent with HTML. MDN documents the |
👍 I think we should push Tell me if you still want to work on this @rootwork I might have some times to open a PR for that at the end of the week |
I think this should be good in 4.12 👍 |
hey @iRyusa , can i check that a global lang tag has been added? our (company) system uses "mjml-browser": "^4.10.4", not the current 4.14.x and i cant find any documentation to support that lang has been added. thus i don't know if it's worth asking our sys admin to up our mjml version 🤔 |
You can check release note it's available since 4.13 https://github.com/mjmlio/mjml/releases/tag/v4.13.0 |
Is your feature request related to a problem? Please describe.
From @hteumeuleu https://github.com/hteumeuleu/email-guidelines#lang:
MJML currently accepts a
lang
attribute on<mjml>
, which it places on the root<html>
element, but it does not accept one on the<mj-body>
element, which would map to the containing<div>
element that it creates.Describe the solution you'd like
Allow for
lang
on<mj-body>
.Describe alternatives you've considered
The only current workaround that I've found is to nest a
<div>
within every<mj-column>
and set the language there, which is a pain.Additional context
This is arguably an a11y bug, but since it's adding a new enhancement I used the feature issue template.
I'd be happy to do a PR for this if the maintainers agree with the idea.
The text was updated successfully, but these errors were encountered: