summaryrefslogtreecommitdiff
path: root/searx/static/themes/simple/src/less/toolkit.less
AgeCommit message (Collapse)Author
2021-10-18[simple theme] define device width with less vars in defenition.lessMrPaulBlack
2021-10-09[simple theme] new color theme and result on mobile and tabletMrPaulBlack
* clean up vars in defenition * results look now the same on mobile and desktop * reworked results on mobile * new color theme with more vibrant colors
2021-10-09Redo Color Theme and css cleanupMrPaulBlack
* remove vars and add elements to base and btn vars * change default border radius to 10px and padding to 0.7em * put border radius and padding on search input form, infoxbox and buttons * remove unused .help class in #categories_container * remove active background from tabs to straemline design * redo search form: 10px padding * 2rem margin on search results on desktop * fix modal pacement of engine reliability in prefs * use darker accent colors * streamline autocomplete with more padding and a hover effect
2021-10-09[theme] replace all hardcoded colors by css vars and drop ununsed varsMrPaulBlack
2021-10-09[theme] convert less vars to css vars in simple themeMrPaulBlack
2021-09-27[theme] margin around checkboxes is bigger now, index centers the search ↵MrPaulBlack
more and the pref, stats and about page have a max-width now
2021-09-27[theme] cleanup grid layout and remove various margins and paddings from ↵MrPaulBlack
elements
2021-09-27[fix] make selected tabs not change wifth anymore compared to not being selectedMrPaulBlack
2021-06-24[stylelint] disable role 'no-descending-specificity'Markus Heiser
This patch disables role 'no-descending-specificity'. IMO it is better to have this rule active (see below [1]), but it is hard to rewrite the less files to pass this rule, so for the first I chose to disable this rule. --- Source order is important in CSS, and when two selectors have the same specificity, the one that occurs last will take priority. However, the situation is different when one of the selectors has a higher specificity. In that case, source order does not matter: the selector with higher specificity will win out even if it comes first. The clashes of these two mechanisms for prioritization, source order and specificity, can cause some confusion when reading stylesheets. If a selector with higher specificity comes before the selector it overrides, we have to think harder to understand it, because it violates the source order expectation. Stylesheets are most legible when overriding selectors always come after the selectors they override. That way both mechanisms, source order and specificity, work together nicely. This rule enforces that practice as best it can, reporting fewer errors than it should. It cannot catch every actual overriding selector, but it can catch certain common mistakes. [1] https://stylelint.io/user-guide/rules/list/no-descending-specificity/ Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-24[stylelint] simple theme: fix some errors reported by stylelintMarkus Heiser
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-24[fix] simple theme: use stylint to fix common lint errorsMarkus Heiser
This fix was autogenerated by:: npx stylelint -f unix --fix 'searx/static/themes/simple/src/less/**/*.less' Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2021-06-16[mod] simple theme: move source files to the src directoryAlexandre Flament