-
Notifications
You must be signed in to change notification settings - Fork 974
Wrong favicon is shown for bookmark #1646
Comments
I notice sometimes this too |
happens sometimes in mine |
steps to reproduce wanted if anyone can find them. |
I think I found out how to reproduce, you need to click a bookmark item and before it is done loading click another one. |
there's no way to fix your previous entries. |
it just won't happen anymore. |
Ok, confirmed fixed |
Re-opening as this is still happening |
Looked into this briefly; I know the favicons are now updated properly after page visit. My best guess is that the favicon for site A is being updated (an event which fires after page load and sets after looking up site using index) while a site B is being added (and added to the sites array) |
+1 from support |
+1 from support |
Possibly related to #10176 @NejcZdovc I believe this will be fixed with your PR (#10136). What do you think? |
Yes this should be fixed with #10136 |
Resolves #1646 Resolves #1856 Resolves #2655 Resolves #2771 Resolves #3646 Resolves #3694 Resolves #4224 Resolves #4260 Resolves #4833 Resolves #4868 Resolves #4929 Resolves #5072 Resolves #5699 Resolves #5382 Resolves #6104 Resolves #6108 Resolves #6585 Resolves #8022 Resolves #9301 Resolves #9326 Resolves #9978 Resolves #10026 Auditors: Test Plan:
Resolves brave#1646 Resolves brave#1856 Resolves brave#2655 Resolves brave#2771 Resolves brave#3646 Resolves brave#3694 Resolves brave#4224 Resolves brave#4260 Resolves brave#4833 Resolves brave#4868 Resolves brave#4929 Resolves brave#5072 Resolves brave#5699 Resolves brave#5382 Resolves brave#6104 Resolves brave#6108 Resolves brave#6585 Resolves brave#8022 Resolves brave#9301 Resolves brave#9326 Resolves brave#9978 Resolves brave#10026 Auditors: Test Plan:
Test plan
#10136 (comment)
Sometimes favicons get mixed up. In the above screenshot, the favicon for feedly was green while I was reading the RSS feeds. Then I clicked the twitter link and the feedly favicon changed to that of twitter.
The text was updated successfully, but these errors were encountered: