Today was the first day in my "office" (the local hackerspace) working on qutebrowser, and day 2 of the crowdfunding in total!

Right now I'm preparing some things for the new config to be possible, and also finishing some work related to QtWebEngine and Qt 5.9.

Here's what happened since the weekend:

• Stickers for backers who don't have a t-shirt are all sent out. Let me know when you get them!
• The check for the unsupported Nouveau graphic driver with QtWebEngine is now more stable and also can be used from an already running instance with :debug-console.
• Some reply object tracking which was originally introduced to help with segfaults on exit with old Qt versions was removed as it's not needed anymore, and caused problems with the PyQt 5.9 snapshots.
• Download error messages are now displayed with QtWebEngine on Qt 5.9. I've had this patch lying around for a while, but now I could finally test it with an updated PyQt.
• Chromium logging messages occurring during tests are now properly parsed and updated for Qt 5.9.
• The way defaults are handled for settings passed to the web backend was refactored so they don't require a getter anymore (which would've gotten difficult with the new settings, as there's no one true value anymore).
• While working on that, I noticed clicking an element via javascript didn't use the right setting object when using private browsing, so I fixed that.
• Some settings which (according to past crash reports) almost nobody did modify were removed or merged.
• A setting got renamed to make clearer what it does. I expect to rename many more settings at a later point though.
• A pull request adding a {private} field to the window-title setting was accepted.

Tomorrow, I plan to take a closer look at a quite big pull request (maybe even the biggest in qutebrowser's history?) refactoring most of the completion code and fixing many issues in the process. Unfortunately it has some performance issues, but I'd really like to get it in before starting the big config rewriting.