a month later

Qutebrowser updated to 1.10.2 in wip, only supported back-end qt5-qtwebkit due to the mess with qt5-qtwebengine

11 days later

I was bored...,
wip/qutebrowser updated to 1.11.0 😉

    pin also try swisscow.com for search engine it's fast 😄

    “Only the paranoid survive.”

    ― Harold Finch
    NetBSD VPS , NetBSD , OS108

        johnb .com works too 🙂

        “Only the paranoid survive.”

        ― Harold Finch
        NetBSD VPS , NetBSD , OS108

          4 days later
          a month later

          Updated to 1.12.0

          are you going to commit this?

          • pin replied to this.

            nia I would like to but, at the moment I've only enabled support for qtwebkit, as qtwebengine is broken.
            Upstream plans to drop support for qtwebkit once Qt hits version 6, unless development of qtwebkit gets up-to-date, see https://github.com/qutebrowser/qutebrowser/issues/4039
            So, honestly I don't know if I should commit?
            Thoughts?
            Is anyone working on qtwebengine?

            • nia replied to this.

                pin I replied to the issue. Looks like funding annulen might be a viable way forward?

                • pin replied to this.

                    nia I saw the comment. Yes, founding annulen could be a solution but, porting qtwebengine also. I know, ...it's a huge mess. Just looking at FreeBSD's amount of patches makes me sick.
                    The thing is, I've installed Alpine on bare metal just to check and, the browser works much smoother with qtwebengine than it does with qtwebkit ...actually, in general, anything webkit based "eats" my cpu in a way, that makes it nearly unusable.

                      That might be a mistake in the way we're building it... Chromium and WebEngine need some features that won't be available until NetBSD 10 at least.

                      • pin replied to this.

                        nia back to the commit question, I've noticed otter-browser is also using qtwebkit backend and its in pkgsrc proper, so I no longer see why qutebrowser shouldn't?
                        I could push the package, though I'm a bit afraid of negative reactions.

                        • nia replied to this.

                            pin I doubt there will be any, since we'll likely be shipping firefox52 alongside newer versions for eternity.

                            • pin replied to this.
                            • Jay likes this.

                                nia we'll likely be shipping firefox52 alongside newer versions for eternity.

                                😅

                                nia might be a mistake in the way we're building it...

                                qutebrowser, midori, vimb and surf-git, all behave the same on my machine 🙁
                                Do you also experience this? firefox68 and seamonkey are fine, it only happens with webkit based browsers. Although, IIRC it also happens on Linux 🤔

                                If you think I should commit qutebrowser, I can do it tomorrow, ...today its not possible as I don't have access to my laptop.

                                    Are you sure it wasn't fixed in webkit-gtk 2.28.2?

                                     - Fix excessive CPU usage due to GdkFrameClock not being stopped.

                                    it seems about the same idle as firefox here.

                                    • pin replied to this.