-
Notifications
You must be signed in to change notification settings - Fork 278
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Favicon indicator is not working correctly in Chrome on Mac #99
Comments
To clarify, it works fine in Windows. I think it's an issue with Macs. |
Also, I made sure that only a standard favicon.ico file shows up in the HTML, and the issue still occurs, so I don't think it has to do with the file format, but something else. |
FWIW, in case anyone else has this issue, I was able to resolve this by rolling back the TinyCon.js file to v0.5. The issue may be with the latest update. |
jasonluttrell
changed the title
Favicon indicator are not working correctly in Chrome
Favicon indicator is not working correctly in Chrome
Oct 13, 2020
jasonluttrell
changed the title
Favicon indicator is not working correctly in Chrome
Favicon indicator is not working correctly in Chrome on Mac
Oct 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm using a Drupal module (Environment Indicator) that uses the TinyCon library. The favicon function does not seem to be working correctly in Chrome.
There is a little "T" next to a square color, instead of overlaying. See image.
This works fine in every other browser. It also worked fine in Chrome on my local computer. I can't tell what changed. Perhaps I updated the image and that caused it to stop working? Is there a specific file format, dimensions, file size, etc. that are required for it work right in Chrome?
I tried the change in a previous issue #96, but it made no difference. I have also closed my browser and flushed my cache.
Thanks.
The text was updated successfully, but these errors were encountered: