Florian Bruhin 3179e8c7b9 Always autoescape jinja environments unless overridden ... We were only rendering .html files before, so the old _guess_autoescape function had the effect of always autoescaping .render() (from a file) but never autoescaping .from_string(). However, most places using .from_string() actually render (Qt-)HTML via jinja, so they should escape stuff! Now, we always autoescape, except when the caller uses the jinja.environment.no_autoescape() context manager, which places rendering stylesheets now do. This impacted: - Confirm quit texts (no HTML here) - config.py loading errors (where this was found because of an error containing - a <keybinding>) - Certificate error prompts (should be fine from what I can tell, as the only user-controllable output is the hostname, which cannot contain HTML)		2017-09-16 10:43:59 +02:00
..
end2end	Resurrect :debug-cache-stats test	2017-09-15 14:16:42 +02:00
helpers	Fix lint	2017-09-15 17:24:39 +02:00
manual	Update some more references to old config options	2017-07-04 16:46:02 +02:00
unit	Always autoescape jinja environments unless overridden	2017-09-16 10:43:59 +02:00
conftest.py	Get rid of init_standarddir fixture	2017-09-15 14:30:46 +02:00
test_conftest.py	Finally update copyrights...	2017-05-09 21:37:03 +02:00