-
Notifications
You must be signed in to change notification settings - Fork 142
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
Feature/32702 #247
Feature/32702 #247
Conversation
…: Invalid expression invendor/pelago/emogrifier/Classes/Emogrifier.php on line 269 by remoqinv @charset UTF_8
I think we should ask for changes in the mentioned M2 dependency, b/c replacing this in this way is not so elegant and didn't fix the issue for everyone. Related issue: MyIntervals/emogrifier#296 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's limit this just to email-inline file and I'm okay to merge it.
As a workaround we created a Composer patch:
|
@Igloczek what do you think? I think better to make as you said - just limit this replace to one css file |
Magento Open Source 2.3.0 Release Notes Emogrifier dependency has been updated to ^2.0.0. Fix submitted by Oliver Klee in pull request 13351. |
@Stevie-Ray great. However I will still add extra task next week for email-inline.css only so if someone would need it (like previous M2 versions etc) he can use it. |
…e from scss helper (gulp styles task) to separate task email-fix
@Igloczek tested |
Pelago/emogrifier is used for transforming email-inline css into inline css inside email content that later is send to the customer by Magento. It has some limitation related to selector and special character and
@charset "UTF-8";
is one of the problem. However not sure if my solution is the best - maybe some "if" to remove it only for flagged files like email* ?