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
According to the issue I mentioned, this encoding is done when calling DomDocument::saveHTML() so it's not related to twig. I'm not sure there is a way to configure DomDocument to leave href values unencoded.
I think there should be a warning in the docs regarding the use of inlinecss tags.
Activity
cordoval commentedon Dec 1, 2017
what do you think is the reason to encode whatever is inside of the hrefs?
disregarding this, do you know if any other twig tree node parsing/rule does the same to the hrefs? or it is just this implementation?
I would say don't use it, and use the service and method calls. That is what i do.
icedevelopment commentedon Dec 4, 2017
According to the issue I mentioned, this encoding is done when calling DomDocument::saveHTML() so it's not related to twig. I'm not sure there is a way to configure DomDocument to leave href values unencoded.
I think there should be a warning in the docs regarding the use of inlinecss tags.