Ryan Roden-Corrent 66cc5f5ea4 Add support for more values in QtColor config type. ... Recent changes in the completion highlighter mandate that config.val.colors.completion.match be changed from a QssColor to a QtColor. However, the latter accepts fewer formats. To avoid breaking configs, this allows QtColors to be specified using all the same formats as QssColors, excluding gradients. I separated the QssColor and QtColor tests as the previous approach of generating the tests made adding tests for QtColor more complicated. While working on this I discovered that Qt's css parser is potentially broken around parsing hsv percentages and filed https://bugreports.qt.io/browse/QTBUG-70897. For consistency, I made our parser similarly broken. You can show the bug in qutebrowser right now by noting that the following have different effects: ``` set colors.completion.odd.bg 'hsv(100%, 100%, 100%)' set colors.completion.odd.bg 'hsv(358, 255, 255)' ```		2018-10-02 17:30:43 -04:00
..
test_config.py	Fix test_set_wrong_backend	2018-07-02 22:32:59 +02:00
test_configcache.py	Fix pylint issues with config cache	2018-09-06 16:43:10 +02:00
test_configcommands.py	Fix docstrings	2018-09-02 15:46:57 +02:00
test_configdata.py	Run test_init_benchmark on CI again	2018-02-10 19:50:20 +01:00
test_configexc.py	Improve error messages with backend conditionals	2018-06-12 11:10:03 +02:00
test_configfiles.py	Add additional test	2018-06-09 19:57:22 +02:00
test_configinit.py	Fix checks for Nouveau workaround	2018-07-19 00:28:12 +02:00
test_configtypes.py	Add support for more values in QtColor config type.	2018-10-02 17:30:43 -04:00
test_configutils.py	Whitelist config options which support URL patterns	2018-02-20 23:26:22 +01:00