|
Finally the dark UI is here but in the logger, all is still horrible. |
Replies: 22 comments 41 replies
Elaborate on what is "horrible". |
How is this constructive? To be constructive you need to be very specific about what needs to be fixed, otherwise we have no idea what you think requires fixing, and no action taken as a result. |
|
Blinking white background when dark theme is active. DetailsuBlock Origin: 1.40.9rc0
Chromium: 98
filterset (summary):
network: 96192
cosmetic: 62224
scriptlet: 18070
html: 0
listset (total-discarded, last updated):
default:
user-filters: 0-0, never
RUS-0: 41141-9, 7m
easylist: 62829-20, 7m
easyprivacy: 26696-113, 7m
plowe-0: 3677-822, 7m
ublock-abuse: 77-1, 7m
ublock-badware: 3831-72, 7m
ublock-filters: 30183-181, 7m
ublock-privacy: 194-2, 7m
ublock-unbreak: 1699-39, 7m
urlhaus-1: 7611-0, 7m
filterset (user): [empty]
modifiedUserSettings: [none]
modifiedHiddenSettings: [none]
supportStats:
allReadyAfter: 359 ms (selfie)
maxAssetCacheWait: 229 ms
popupPanel:
blocked: 1
blockedDetails:
github.com: 1 |
|
@happysurf provide an exact URL which I can use to reproduce exactly what you get in your logger. Ok I forced an update of one of uBO's list, and tabless network requests shows up fine in dark mode, i.e. light text on dark background, so I can't still reproduce that illegible line in your screenshot. |
|
Since we're talking about the logger's dark UI, may I request some changes?
mediumblue is rather hard to read on a dark background. Especially when looking from a distance, suffering from eye-strain or generally for people with slightly worse vision.blue is only slightly better - I'm proposing changing it to something like deepskyblue or cyan, if we need to stay with blue variants.
Changing the color to one of these lighter hues will also kinda fix the issue with shadowed web workers as mentioned in @happysurf 's comment and @uBlock-user 's reply.
Screenshots
Could we get these fixed, please? |
|
The link for try the logger is https://pixcut.wondershare.com/account.html |
Just to be clear, in the main commit for dark mode, I pointed out that I don't expect it to be complete everywhere, there is a lot of corners in uBO, and that I will fix as per feedback -- this is what we are doing here. So if you see a bad color choice, it's not because I thought this was a good idea, it's just something which I overlooked -- there were a huge amount of CSS-related changes and at some point I had to commit what I had without waiting to have 100% coverage by trying to find everything on my own. |
|
Dark theme is not applied after session restore. Both in dashboard and logger window. Firefox 98.0a1, 1.40.9rc1, system and browser set to default theme (light). |
|
The Click2Load text is not visible.
|
|
A minor cosmetic issue - any chances for a slightly higher contrast between the background and the font in Picker's counter? Be it either a darker background or a darker (black?) font. I know these haven't changed since the Light theme, but I think it's just a tad more difficult for the eye to adjust to white on light grey from the darker colors everywhere else than it is on the light theme. Though, I also did have trouble (on occasion) reading the numbers on there in the past (due to eye strain or wherever). |
|
Just thinking out loud here, but do you think using Perhaps using Also, not entirely related, but I was wondering if using 4 color variables for |
|
Adding |
|
Could |
|
Logger's |
|
In the dark theme, the noop rules in the popup panel have reversed colors - inherited ones are dark gray. |
|
A very minor issue. In the logger, when on the "All" tab, the message about filter lists being reloaded is nearly invisible with its dark blue font color on a dark grey background. |






















Just to be clear, in the main commit for dark mode, I pointed out that I don't expect it to be complete everywhere, there is a lot of corners in uBO, and that I will fix as per feedback -- this is what we are doing here. So if you see a bad color choice, it's not because I thought this was a good idea, it's just something which I overlooked -- there were a huge amount of CSS-related changes and at some point I had to commit what I had without waiting to have 100% coverage by trying to find everything on my own.