Issue #1334
The problem was that there were too few slashes. On Linux, absolute
paths start with /, so
file:// + /home
gives file:///home, which is a valid path. On windows however, absolute
paths start with a drive letter, so
file:// + C:/Users
gives file://C:/Users, which is parsed as "host C, path Users", which is
why it could be written as file://c/Users (strip out the empty "port"),
giving us an invalid path.
The solution is to add the third slash in the template, and strip the
redundant slash on unix systems.
Additionally, this fixes a bug where navigating from '/home/' to the
parent directory would give '/home' instead of '/'
We can get UndefinedError when a new function got added to the jinja
env (and gets called from a template) and the user did update the
on-disk templates but not restart qutebrowser yet.
In this case, let's show a special error page to the user and tell them
to do :report in the unlikely case it's actually a bug.
Fixes#1362.
See #1360.
Fix to make sure the js bridge code is only enabled when qute: pages are shown.
Previously it would only be available to the first page (and before that it
was available to all pages).
Add the ability to view/edit the browser's config settings via a special
browser page.
It's very simplistic for now, but a good starting point.
Future possibilities:
* Matching config types to html input types
* colors = html colorpicker
* options with valid_values = select/multi-select
* plain text fallbacks where appropriate
* multi-line text edits for long options (i.e. host-block-lists)
* Javascript option verification
* switch from submitting changes onblur to onchange if an option passes basic
verification, etc.
