Qutebrowser 1.0.0 released

Major changes include dropping legacy qt, legacy qtwebkit, and older python. Now you have to have qt 5.7.1 and python 3.5 minimal. Qtwebengine is now the default, but you still have qtwebkit if you have the updated version and it'll be used if qtwebengine isn't installed.
qutebrowser.org/CHANGELOG.html
github.com/qutebrowser/qutebrowser/releases
Expect distros to update soon. If you're on older distro like debian 8 or ubuntu 14.04 consider your distro dropped unless you want to maintain dependencies yourself.

Other urls found in this thread:

github.com/qutebrowser/qutebrowser/issues/27
github.com/qutebrowser/qutebrowser/issues/28
github.com/qutebrowser/qutebrowser/issues/2626
github.com/qutebrowser/qutebrowser/issues/927
qupzilla.com/
github.com/qutebrowser/qutebrowser/issues/335
en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
youtube.com/watch?v=Z4kQfBnVc_A
twitter.com/SFWRedditVideos

Does it support uMatrix and Tree Tabs yet?

>yet another shit browser
Wew lad

This browser has been around for quite a while and it's good, low quality shitposter

It's bloat of wheels.

I don't know what your definition of bloat is, but pretty much every browser could be considered bloated because of how the current web is. Even the suckless browser has to deal with webkitgtk which they despise but need it if they want a usable web browser.

It uses qtwebengine by default now, so I would assume it also supports plugins made for chromium

botnet

Wasn't the big thing with the 1.0.0 release. Per site/domain settings so we could use custom css?? I don't see this mentioned in the release notes. I stopped using this browser because of the lack of this feature. I was really happy to see that the developer kickstarted a funding and promised to implement it. The poor kid took the money he raised and got eye surgery. Spent six months in "re-inventing" the not broken at all configsystem.

Lua-kit has been the better alternative all a-long for people to lazy to set up surf/uzbl. But had some issues with luakit and thought I'd wait for the qutebrowser release. Fuck this. Will never fund a similar project. And will take the 2-hours to get surf work with hints ans custom css.

>As announced previously, per-domain settings unfortunately didn't make it into v1.0.0 - it's the next thing I plan on tackling. However, there's more than enough big things in v1.0.0! :)

From a Kickstarter project update from today. I'm happy with where the browser currently is though (been using the QtWebEngine backend for ages) and hopefully it will only get better.

Nothing uMatrix-like yet, but at least basic functionality should work once per-domain settings are in. See:
github.com/qutebrowser/qutebrowser/issues/27
github.com/qutebrowser/qutebrowser/issues/28
github.com/qutebrowser/qutebrowser/issues/2626

You can do ":set tabs position left", but there's no real tree yet. Someone started some work on that, but didn't seem interested in actually cleaning it up and getting it into qutebrowser unfortunately: github.com/qutebrowser/qutebrowser/issues/927

Nope, QtWebEngine doesn't support Chromium extensions.

You can already use custom CSS, just not per-domain. Like mentioned (and earlier kickstarter updates did too), I didn't manage to finish everything I planned in the month of full-time work I did. Planning how much time implementing something will take isn't always easy.

>The poor kid took the money he raised and got eye surgery.

Switzerland has a working public health system, I basically pay nothing for that surgery. And it's something which has been planned and scheduled for much longer than the Kickstarter was.

>Spent six months

One month.

> "re-inventing" the not broken at all configsystem

You have no idea.

>Lua-kit has been the better alternative all a-long for people to lazy to set up surf/uzbl. But had some issues with luakit and thought I'd wait for the qutebrowser release.

FWIW luakit has seen quite some activity again in the past few months. Feel free whatever you're happy with, I couldn't care less.

>tfw have to switch to this because there's no viable addon like vimfx for firefox after 57

I'm using Qutebrowser and so far I like it. I wish there was a script blocker like "no-script".

The best part of the browser is the fact that you're so involved with the community/users. Always nice to hear from you.

Still waiting for something like umatrix, but it's looking very promising.

That'll come with per-domain settings.
github.com/qutebrowser/qutebrowser/issues/27

Thanks!

Yeah, it's a feature I really want as well (I have it installed in Chromium), but unfortunately things just aren't there yet.

Qutebrowser just need ublock origin, umatrix, https everywhere, and greasemonkey and it's perfect.

Throw in tree tabs and I'll agree with you 100%

I just installed the 1.0 release for win64 and the command line seems to be cut off.
In fact, it appears as if the window is cut off on all sides. Instead of drawing the program on the inside of the window decoration, it looks like it's drawing the program on the outside of the window decoration not considering that the window decorations ommit the view.

That's weird, but is most likely a Qt bug and not a qutebrowser one. It's not something I've ever seen (or heard about) before though...

I assume you see the same with v0.11.0?

> most likely a Qt bug and not a qutebrowser one.
That's what I figured, so I posted here before bothering with a github issue. I'll try 0.11 in a moment.

Same thing with 0.11.0. All 4 sides are cut off by the width/height of the window decorations.
Windows 7 by the way.

Does any of this mean it's going to get add-ons and finally have an ad blocker? That's the real reason I'm not using this as my standard web browser.
Same here, although VimFx still works on Pale Moon.

Hey the-compiler, are you going to keep the requirements at python 3.5 and qt 5.7?

Odd. Can you check whether you see the same with QupZilla? See qupzilla.com/

It has a (host based) adblocker since 3 years already (run :adblock-update to update it). Yes, a Python plugin API will come at some point, but I can't say when.

Qt 5.7.1 - but yes, probably for the next two years or so.

Good because gentoo is getting close to stabilizing python 3.5 and I didn't want requirements to be increased within a matter of months.

same thing with QupZilla (portable installation).

Gentoo/Debian/Ubuntu are the reason for those minimum versions. I originally wanted to wait until Gentoo stabilized 3.5 before dropping 3.4, but then decided to go for it anyways.

Have you thought about automatic http to https with qutebrowser? Or would that be something that qtwebengine would have to do?

There are basically two solutions to that problem:

1) Trying HTTPS and falling back to HTTP. This is something I can't implement because I can't integrate into QtWebEngine that deeply.

2) Having a list of rules to rewrite URLs, like HTTPS Everywhere does. This should be possible (but some work, as HTTPS Everywhere uses JavaScript regexes), and there's an issue tracking it here: github.com/qutebrowser/qutebrowser/issues/335

Oh, and there's HSTS to let servers force HTTPS connections on the first connection: en.wikipedia.org/wiki/HTTP_Strict_Transport_Security - that's already supported.

lasik? did you get dry eye?

why not add webextensions support instead of reimplementing every addon from scratch?

No, strabism surgery. See the crowdfunding video at youtube.com/watch?v=Z4kQfBnVc_A for how it looked before, now it's almost unnoticable.

Because you don't just "add WebExtension support". It's taken Mozilla months with a big development team.

Partial support for some simple extensions might be possible (or maybe even things like uBlock), or they might not. I haven't looked into it yet.