-
-
Notifications
You must be signed in to change notification settings - Fork 539
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
unloaded pinned tabs do not show website icon #2789
Comments
Hey @speedy1804! I'm here to help you with any bugs, questions, or contributions you have. Let's get this sorted out together! The issue with pinned tabs losing their website icons might be related to recent changes in the favicon fetching logic. In the latest update (1.0.1-a.18), the code attempts to fetch favicon data for each pinned tab using To troubleshoot, you might want to check if the favicon fetching process is encountering any errors or if there are network issues preventing the fetch. Additionally, ensure that the URLs being pinned have accessible favicons. If the problem persists, it could be beneficial to look into any recent changes in the |
Can reproduce, I have my pinned tab settings to close and reset the tab to its default state when using ctrl+w. It removes the icons. |
Having this same issue. |
Same here! |
Same here. It looks like this issue was fixed by this PR, which is included in the latest Zen Twilight build: |
Hi, @speedy1804. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale. Issue Summary:
Next Steps:
Thank you for your understanding and contribution! |
this has been fixed with the beta release |
Thank you for your contribution, speedy1804! We appreciate your help in keeping our issues organized. |
Captchas
What happened?
As you can see, the website icons aren't shown. I don't know if this has anything to do with the latest update (1.0.1-a.18), as I've only been using pinned tabs since this update.
The way I handle my pinned tabs:
Steps to reproduce:
Reproducible?
Version
1.0.1-a.18
What platform are you seeing the problem on?
Windows
Relevant log output
No response
The text was updated successfully, but these errors were encountered: