qutebrowser/qutebrowser/completion
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
..
models Fix configmodel nitpicks 2017-09-07 08:56:11 -04:00
__init__.py Finally update copyrights... 2017-05-09 21:37:03 +02:00
completer.py Quote a completed value if it contains " 2017-09-15 22:17:38 +02:00
completiondelegate.py Always autoescape jinja environments unless overridden 2017-09-16 10:43:59 +02:00
completionwidget.py Merge remote-tracking branch 'upstream/master' into HEAD 2017-08-06 18:13:49 -04:00