Specify MimeType to always use for ajax templates #742
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For twig.js to be used in the browser, it requires the user to know that they either must name their templates as an ending that browsers recognized (e.g.
txt
orhtml
) or to manually register a mime-type to the.twig
extension. Otherwise, when fetching a template, a browser will attempt to parse it usingtext/xml
which can cause issues depending on strictness (e.g. #741).This PR changes it so that twig.js always specifies that templates received via XMLHttpRequest are
text/plain
and to be treated as such.