rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
16,200 Commits 1 Branch 0 Tags 112 MiB
6fa07703db
Commit Graph

16200 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Florian Bruhin
6fa07703db More flaky tests 2018-07-24 19:56:34 +02:00
Florian Bruhin
12e5375931 Handle more test flakiness 2018-07-24 17:36:07 +02:00
Florian Bruhin
8b814e3072 Increase qute://history delay in tests 2018-07-24 16:51:36 +02:00
Florian Bruhin
32e957dfbd Update security FAQ entry 2018-07-24 16:15:54 +02:00
Florian Bruhin
d62a70267e Update changelog 2018-07-24 16:05:03 +02:00
Florian Bruhin
d830dd69a4 Add workaround comment 2018-07-24 16:04:28 +02:00
Florian Bruhin
90d7ab84b0 Merge remote-tracking branch 'origin/pr/4072' 2018-07-24 16:03:54 +02:00
Florian Bruhin
f69cd2259e Don't require user interaction for clicking qute:// links 
See #4090, #4073
 2018-07-24 15:44:27 +02:00
Florian Bruhin
1413c910c6 Update changelog 2018-07-24 15:42:14 +02:00
Florian Bruhin
e70d796dad Merge remote-tracking branch 'origin/pr/4090' 2018-07-24 15:41:40 +02:00
Florian Bruhin
0e46afb6de
Merge pull request #4091 from qutebrowser/pyup-scheduled-update-2018-07-23 
Scheduled weekly dependency update for week 29
 2018-07-24 15:38:43 +02:00
Florian Bruhin
6c353a140f Bump up yaml_load deadline on CI 2018-07-23 21:32:09 +02:00
pyup-bot
05bf5a7ce8 Update pytest-repeat from 0.4.1 to 0.5.0 2018-07-23 19:34:17 +02:00
pyup-bot
a8974e1f04 Update hypothesis from 3.66.1 to 3.66.6 2018-07-23 19:34:15 +02:00
pyup-bot
f5649730ce Update pylint from 2.0.0 to 2.0.1 2018-07-23 19:34:14 +02:00
pyup-bot
4c8e163166 Update astroid from 2.0 to 2.0.1 2018-07-23 19:34:12 +02:00
Florian Bruhin
98cf1e5b2c Kill some more tests 2018-07-22 17:19:12 +02:00
Florian Bruhin
463dd911a3 More flaky tests 2018-07-22 15:46:24 +02:00
Florian Bruhin
40e58126aa About everything is flaky 
Did I already mention that I'm starting to hate those tests I wrote in the past
with a passion?
 2018-07-22 14:05:40 +02:00
Florian Bruhin
c1c182d958 Mark more tests as flaky 2018-07-22 13:03:25 +02:00
Florian Bruhin
0304036d7d Skip test which is too flaky 2018-07-22 12:05:55 +02:00
Florian Bruhin
13f688eeb8 "Fix" more flaky tests 2018-07-22 11:24:06 +02:00
Florian Bruhin
a7170fefe9 Turn off hypothesis deadline if on CI 2018-07-22 10:13:06 +02:00
Jay Kamat
230dd6b4ea
Merge pull request #4080 from cryzed/qute-pass-follow-symlinks 
[qute-pass] Follow symlinks when finding pass candidates
 2018-07-21 15:11:52 -07:00
Florian Bruhin
31a6374e0e Mark some more flaky tests as flaky 
I really want end2end tests to die...
 2018-07-21 23:36:45 +02:00
Florian Bruhin
733625e140 Stabilize test_qute_settings_persistence 2018-07-21 23:36:45 +02:00
Jay Kamat
31d318ee0a
Add catch and error handling for errors in follow_selected click 2018-07-21 13:58:41 -07:00
Florian Bruhin
d0412811d2
Merge pull request #4089 from jgkamat/jay/audible-tab-refactor 
Move audible strings into class variables
 2018-07-21 21:59:19 +02:00
Jay Kamat
2b8068f6da
Move audible strings into class variables 2018-07-21 12:50:45 -07:00
Florian Bruhin
3b6c4d4b85 Remove unneeded log prefix 
We see the function anyways
 2018-07-19 00:31:40 +02:00
Florian Bruhin
7d695d40b9 Add a QUTE_FAKE_OPENGL_VENDOR envvar 2018-07-19 00:31:23 +02:00
Florian Bruhin
a8e2a04648 Update changelog 2018-07-19 00:28:51 +02:00
Florian Bruhin
8a748741ba Fix checks for Nouveau workaround 2018-07-19 00:28:12 +02:00
cryzed
9ea6f4acf4 Follow symlinks when finding pass candidates 2018-07-18 16:18:56 +02:00
Florian Bruhin
1d9ee2c11d Recompile requirements files 2018-07-18 09:58:49 +02:00
Florian Bruhin
a72eee8e39 Enable XSS auditing by default 
Qt disables this by default, but Chromium does have it enabled.

I also submitted a change to Qt to hopefully enable it by default there
starting with Qt 5.12: https://codereview.qt-project.org/#/c/198354/15

This also removes the claim of having a (big) performance impact, as Chromium's
XSS design doc says the opposite:
https://www.chromium.org/developers/design-documents/xss-auditor
 2018-07-17 12:01:17 +02:00
Florian Bruhin
b8c70e5986 Rewrite type comments again 2018-07-16 22:35:40 +02:00
Florian Bruhin
03ac3b4d7d Update to pylint 2.0 2018-07-16 15:09:06 +02:00
Florian Bruhin
8e6aa9e3e1 Locally disable assignment-from-no-return for pylint 2.0 2018-07-16 14:53:30 +02:00
Florian Bruhin
2d65f25a04 Remove unnecessary object inheritance 2018-07-16 14:44:31 +02:00
Florian Bruhin
e4a772c61c Fix try-except-raise for pylint 2.0 
See https://github.com/PyCQA/pylint/issues/2302
 2018-07-16 14:44:07 +02:00
Florian Bruhin
e0f3285f05 Fix bad-indentation issues for pylint 2.0 
See https://github.com/PyCQA/pylint/issues/2301
 2018-07-16 14:41:18 +02:00
Florian Bruhin
e50b6912a7 Fix pylint 2.0 useless-return cases 
See https://github.com/PyCQA/pylint/issues/2300
 2018-07-16 14:33:11 +02:00
Florian Bruhin
b1d508a3af Rewrite pseudo "type:" comments for pylint 2.0 
See https://github.com/PyCQA/pylint/issues/2299
 2018-07-16 14:15:00 +02:00
Florian Bruhin
570fe3ed1a Update changelog 2018-07-16 08:17:24 +02:00
Florian Bruhin
9298f3d055 Refactor print handling and fix window.print 
On Qt 5.7.1, window.print() caused a CommandError which wasn't handled as the
command was called from accept_navigation_request.

Instead, we now show the dialog in AbstractPrinting and use that directly.
 2018-07-16 08:16:18 +02:00
Hendrik R
b1a060fb71 Process all events before issuing an alert 
Fixes #2603

The call to processEvents fixes an apparent race condition with some window
managers, e.g. i3. QT seems to be thinking, that the window is not marked as
urgent and toggles it twice, so synchronizing before issuing the alert makes QT
behave correctly.

This change should not change the behaviour on other systems only correct the
fault reported in #2603.
 2018-07-15 14:31:03 +02:00
Florian Bruhin
d1a25b6c3f Release v1.4.1 2018-07-11 17:17:51 +02:00
Florian Bruhin
ae0df2093b Update changelog for v1.4.1 2018-07-11 17:15:32 +02:00
Florian Bruhin
43e58ac865 CVE-2018-10895: Fix CSRF issues with qute://settings/set URL 
In ffc29ee043 (part of v1.0.0), a
qute://settings/set URL was added to change settings.

Contrary to what I apparently believed at the time, it *is* possible for
websites to access `qute://*` URLs (i.e., neither QtWebKit nor QtWebEngine
prohibit such requests, other than the usual cross-origin rules).

In other words, this means a website can e.g. have an `<img>` tag which loads a
`qute://settings/set` URL, which then sets `editor.command` to a bash script.
The result of that is arbitrary code execution.

Fixes #4060
See #2332
 2018-07-11 17:05:23 +02:00