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
..
end2end	Fix lint and test	2018-09-04 23:46:34 +02:00
helpers	Use a shared web_history fixture	2018-09-06 20:08:32 +02:00
manual	Update some more references to old config options	2017-07-04 16:46:02 +02:00
unit	Add support for more values in QtColor config type.	2018-10-02 17:30:43 -04:00
conftest.py	Turn off hypothesis deadline if on CI	2018-07-22 10:13:06 +02:00
test_conftest.py	Update copyright years	2018-02-05 12:19:50 +01:00