-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
[BUG] Default profile image text should be visible in dark mode #9900
Comments
To reduce notifications, issues are locked until they are
🏁 status: ready for dev
|
Thanks for raising the issue, This is happening because the user doesn't exist on GitHub. |
Hey @eddiejaoude, I would like to work on this issue. |
Hey, @j-grosse So, just try changing your profile picture and check whether the issue exists |
Thanks, but it‘s not my profile. If the user has no profile picture on Github an automatically added default placeholder profile image would be the solution. But here the user does not even exist on Github anymore. So there was a picture from the user. Maybe just a very seldom case. Maybe close the issue @eddiejaoude ? |
Thank you @j-grosse It might be that they changed their username. However I do agree and this issue should be closed, which I will do now. |
Has this bug been raised before?
Where did you find this bug?
https://www.biodrop.io/EddieHubCommunity?tab=testimonials
Version of BioDrop (for example "v1.2.3")
v2.95.1
Description
When activating dark mode the grey text in the default profile picture (which is some text) changes to white.
This makes the text (on the white background) disappear.
It is still there as it can be selected, see screenshot.
Steps to Reproduce
Screenshots
Do you want to work on this issue?
No
If "yes" to above, please explain how you would technically implement this
No, as I don't know how to solve this exactly.
When inspecting the profile picture in Google Chrome I see that the style attribute of the img tag ist not set.
In the other profile pictures that are actual images and not text, it is set to style="color: transparent;".
If I add style="color: black;" inside of the inspected img tag, the profile picture becomes visible.
Maybe an automatically added default placeholder profile image instead of default text would be the solution. It would also look better than the cut-off default text.
The text was updated successfully, but these errors were encountered: