Thanks for the heads up. If that's the case I may try to port the design to the simple theme.

If I may ask, what's the reason behind removing Oscar? It seems a lot of users prefer it, myself included.

The reasoning is that oscar is based on bootstrap 3 which is deprecated and its not arbitrary to upgrade to bootstrap 5. (We would first need to upgrade to bootstrap 4 and rewrite part of the templates and then upgrade to bootstrap 5)

The simple theme does not use any HTML frameworks like that and is easier to maintain and also uses more modern CSS approaches for stuff like the image grid for example...
We already put a lot of work over the last few months making the simple theme more modern looking (for example the auto dark theme) and since its also a lot smaller in production we decided to drop oscar (if you use dev tools you can see all the CSS and JS with oscar and how the simple theme is much smaller and needs less JS for the same feature set)

That is the reasoning behind dropping oscar (also the simple theme looks better IMO, but that is personal preference...). In the end the simple theme is much easier to maintain and maintaining 2 themes at the same time with the small dev team on SearXNG core is not feasible IMO.

I see, that makes sense; thanks for explaining.

After that I see no point in keeping oscar 👍

The high contrast settings has issues with FF & Chrome:

• "Simple theme: issue with high contrast FF setting". #951
• https://dev.searxng.org/screenshots.html#config=Chrome+1920+-+high+contrast&test_case=preferences

I think it can be fixed quickly.

Well the fix is the Aria PR is it not?

• Nope, the Aria PR fixes various issues with screen readers (it doesn't change the CSS)
• The fix to the issue 951 is some CSS changes:
  • either by changing how the components are displayed (<select> element)
  • either using dedicated CSS rules ( https://developer.mozilla.org/en-US/docs/Web/CSS/@media/forced-colors )

hmm ok mb.