rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Use upper-case Monospace in test_progress_affecting_statusbar_height

Browse Source 
While the test worked again with eb4691adfc, it
broke again immediately because of 40ee89bddc.

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.
This commit is contained in:
Florian Bruhin 2017-09-12 22:15:50 +02:00
parent b04a233e8d
commit 73ea316501
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/unit/mainwindow/statusbar/test_progress.py
View File

@ -76,7 +76,7 @@ def test_progress_affecting_statusbar_height(config_stub, fake_statusbar,
https://github.com/qutebrowser/qutebrowser/pull/890 https://github.com/qutebrowser/qutebrowser/pull/890
""" """
# For some reason on Windows, with Courier, there's a 1px difference. # 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() expected_height = fake_statusbar.fontMetrics().height()
assert fake_statusbar.height() == expected_height assert fake_statusbar.height() == expected_height