Support

Akeeba Backup for Joomla!

#40652 CSS backend?

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
5.1.0
PHP version
8.1.27
Akeeba Backup version
9.9.2

Latest post by nicholas on Monday, 29 April 2024 09:09 CDT

jjst135

Hi! 

We are in the process of updating sites to Joomla 5. I noticed both Akeeba Backup and Admin Tools are not looking as well as they did before. Maybe the CSS needs some changes? We are using the l'ight mode' for the backend, not the dark mode.

See attached screenshots.

Kind regards,
Jip

 

nicholas
Akeeba Staff
Manager

This is because your computer is set to use a dark theme. Set your computer to a light theme and you'll see everything looks right.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

jjst135

Hi Nicholas,

The whole purpose of adding an option to select 'light mode' in the backend template was to not depend on the system wide settings but to have an option to set the color scheme to light or dark ifrom the backend template. This option was introduced in the latest version of Joomla.

Is it possible to change the extension to follow this setting as well and not use the OS settings?

nicholas
Akeeba Staff
Manager

For what it's worth, your assertion that Joomla is doing it right is patently wrong. The correct way to handle your use case is to change your browser's colour scheme. For Chromium-based browsers it's in Settings, Appearance. In your use case, instead of "System default" (which follows the OS UI dark/light mode preference) you can choose Light for light mode and leave Joomla's setting to "OS preference". This way you are not forcing a colour mode upon your users, you are letting them decide their colour mode preference using the standard way the W3C approved for implementing this feature. Forcing a colour mode site-wide, overriding the user's browser preferences and forcing them to manually transcribe those preferences in a site-specific section (the user profile) is conceptually wrong, and incompatible with the accessibility golden rule that the user knows better than you how they want their accessibility options set up on their own machine.

As to your question on whether it's possible to do something about it, yes, it is.

I will tell you what I've done so far which seems to work well, but I need to test it a lot more before including it in production (which is why it wasn't included in today's release of Admin Tools).

For Admin Tools. Open the file media/com_admintools/css/j5dark.css. Change @media screen and (prefers-color-scheme: dark) with html[data-color-scheme="dark"] and save the file. Clear your browser's cache and reload the page.

For Akeeba Backup. Open the file media/com_akeeba/css/j5dark.css. Change @media screen and (prefers-color-scheme: dark) with html[data-color-scheme="dark"] and save the file. Clear your browser's cache and reload the page.

For completeness' sake, the same applies for Akeeba Ticket System. Open the file media/com_ats/css/j5dark.css. Change @media screen and (prefers-color-scheme: dark) with html[data-color-scheme="dark"] and save the file. Clear your browser's cache and reload the page.

The difference here is that @media screen and (prefers-color-scheme: dark) depends on your OS settings which is what 99.9% of people want. The html[data-color-scheme="dark"] ignores OS settings and ONLY works if Joomla's JavaScript has applied Dark Mode explicitly. The former works on any backend template, the latter only works on Atum if and only if Joomla's JavaScript is loaded.

I will end up having to implement this feature the wrong way (i.e. the way Joomla did) just because Joomla core maintainers can't be arsed to understand accessibility design. Oh, well, what else is new?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

jjst135

As always, a very extensive / detailed answer. Thank you Nicholas. I do understand where you're coming from.

Do I understand you correctly that you will add the changes you outlined in your reply will be included (in some form) to upcoming releases of the extensions?

 

 

 

 

 

nicholas
Akeeba Staff
Manager

Yes, I will add them in the upcoming versions, scheduled for release towards mid to late May.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!