Dark mode on Mac - lastest OS, updated MainWP

Support
1

In dark mode as move mouse up and down page on Managing sites results is flashing white blocks across the screen.

https://www.screencast.com/t/gcolm7mLts1H

2

Taking a wild guess I am going to say Safari ?

Try adding this to your MainWP Custom Dashboard Extension on the CSS tab

.ui.selectable.table tbody tr:hover, .ui.table tbody tr td.selectable:hover {
background: rgba(0,0,0,.95)!important;
color: rgba(0,0,0,.05)!important;

3

Yes on Safari.
I only thing the css acomplished was to change the lite mode row highlight to black.
Which made the meta-text hard to read against the black background.

The white flashing is still happening in dark mode.

4

@techmagick
You can remove that it was a shot in the dark at best…

Are you using any other Dashboard customizations other then the browser dark mode - such as Typemarker?

I’m in the process of testing in Safari Dark Mode soon.

5

Yes have Typemarker installed.

6

@techmagick You will need to reach out to that Plugin Developer @uamv and have them look at their code as MainWP at this time doesn’t support OS/Browser modes.

Typemarker @uamv is a member of this forum - I am sure they will see this and respond - otherwise i suggest opening an official Typemarker support ticket on https://typemarker.com/support/

7

This is a known issue and one that I have no current way of resolving. The MainWP UI does not make use of the CSS :hover attribute in order to apply background styles to those rows. Instead, javascript is used to apply an inline background-color style rule. As such, the !important styles being applied by Typemarker override that inline styles, but only after the browser loads it briefly after it having been dynamically added in the way it is. If anyone has a workaround for that, I’d be happy to get something in a future release.

1 Like
8

@bogdan Is this something that we can tweak so play nicer? IMO, considering we are not in a Node environment, style should be left up to CSS not JS.

9

Yeah, I will look into this. This is actually default behavior for the Semantic UI framework, but I will see what can be done.

2 Likes
10

@bogdan Oh ok kind of figured it would be. Thanks!

11

Yeah, I figured that was probably being pulled in by a default of the framework. Thanks for checking it out!

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.