-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chromium Web Store extension icon notification counter number is not visible properly #101
Comments
Are you using version 1.5+? If so, this is caused by a bug(?) in Manifest V3, see: https://support.google.com/chrome/thread/164964343/chrome-extensions-have-black-dark-box-and-text-for-notifications Edit: I'm not sure if the blame lies on Manifest v3 as some extensions shown in that thread are still using Manifest v2. I can't say what is causing this bug, but the API provides no method to change the badge text color; I'll look into it more later when I have the time. |
After a quick read through https://bugs.chromium.org/p/chromium/issues/detail?id=1321962&q=badge&can=2 I believe this might be an intentional and permanent change. I think the only fix may be to change the badge background color to a color where white is more contrasting than black. |
I am using v1.4.4.2. I have seen this similar issue in another extension where the developer fixed it in later version likely by doing the same thing you mentioned. |
Yep, just had to change the red from #FF0000 to #FE0000. |
This is what the counter looked like before chrome v102 update:
![chrome old icon 01](https://user-images.githubusercontent.com/110061956/181102519-f79662f2-8e98-4ea1-883c-9508feae1356.PNG)
This is what the counter looks like in later chrome versions:
![chrome new icon 01](https://user-images.githubusercontent.com/110061956/181103131-210a8a32-4e36-4909-80c3-788436f400ca.PNG)
I have tried enabling disabling "Pervasive system accent color" chrome flag along with win 10 accent colour setting with no success. As it can be seen in the last pic, other extensions are managing it properly so it should be doable for this extension too & hopefully nothing complicated to implement.
The text was updated successfully, but these errors were encountered: