Keyboard-driven vim-like browser on Qt5
qutebrowser is a keyboard-focused browser with a minimal GUI.
It's based on Python, PyQt5 and QtWebKit and is free software.
- Developed at network
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/qutebrowser && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| qutebrowser-2.5.2.tar.gz | 0006114611 5.83 MB | |
| qutebrowser-2.5.2.tar.gz.asc | 0000000833 833 Bytes | |
| qutebrowser.changes | 0000170380 166 KB | |
| qutebrowser.keyring | 0000070856 69.2 KB | |
| qutebrowser.spec | 0000004152 4.05 KB |
Revision 59 (latest revision is 64)
Dominique Leuenberger (dimstar_suse)
accepted
request 987485
from
Mia Herkt (mia)
(revision 59)
- Update to version 2.5.2
Fixed
* The notification fixes in v2.5.1 caused new notification
crashes (probably more common than the ones being fixed...).
Those are now fixed, along with a (rather involved) test case
to prevent similar issues in the future.
* When a text was not found on a page, the associated message
would be shown as rich text (e.g. after /<h1>). With this
release, this is fixed for search messages, while the 3.0.0
release will change the default for all messages to be
plain-text. Note this is NOT a security issue, as only a small
subset of HTML is interpreted as rich text by Qt, independently
from the website.
* When a Greasemonkey script couldn't be loaded (e.g. due to an
unreadable file), qutebrowser would crash. It now shows an
error instead.
* Ever since the v1.2.0 release in 2018, the
content.default_encoding setting was not applied on start
properly (only when it was changed afterwards).
This is now fixed.
Comments 0