From 73ea31650105f1234778da9ba9200e0da5e29452 Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Tue, 12 Sep 2017 22:15:50 +0200 Subject: [PATCH] Use upper-case Monospace in test_progress_affecting_statusbar_height While the test worked again with eb4691adfce64ff9a6b6e60c48489fa9bfd6db20, it broke again immediately because of 40ee89bddcc863997853cdbf777f9299aa5fe855. With that fix in, the lower-case monospace in the set value was immediately replaced by the full list of fonts again. With an upper-case Monospace, this won't happen. Fixes #2825, for real this time. --- tests/unit/mainwindow/statusbar/test_progress.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/unit/mainwindow/statusbar/test_progress.py b/tests/unit/mainwindow/statusbar/test_progress.py index 91dd4ef18..bada52c12 100644 --- a/tests/unit/mainwindow/statusbar/test_progress.py +++ b/tests/unit/mainwindow/statusbar/test_progress.py @@ -76,7 +76,7 @@ def test_progress_affecting_statusbar_height(config_stub, fake_statusbar, https://github.com/qutebrowser/qutebrowser/pull/890 """ # For some reason on Windows, with Courier, there's a 1px difference. - config_stub.val.fonts.statusbar = '8pt monospace' + config_stub.val.fonts.statusbar = '8pt Monospace' expected_height = fake_statusbar.fontMetrics().height() assert fake_statusbar.height() == expected_height