Notice: You have been identified as a bot, so no internal UID will be assigned to you. If you are a real person messing with your useragent, you should change it back to something normal.
green joined in and replied with this 14 years ago, 4 minutes later, 1 hour after the original post[^][v]#291,931
I only use Opera.
vocalon !:3faggot joined in and replied with this 14 years ago, 1 minute later, 1 hour after the original post[^][v]#291,932
Opera as default browser, but I have all of them installed.
Anonymous F joined in and replied with this 14 years ago, 5 hours later, 7 hours after the original post[^][v]#292,047
@291,921 (A)
The Chrome people don't like to talk about favicons. :( Try suggesting removing favicons from menus or the bookmark bar sometime.
You'd think it would be as simple as finding the code that paints the icon and then throwing in a few changes. No. They seem to have developed a wonderfully convoluted way of deciding whether to pull favicons from the session history, a bookmark data structure, or just downloading it from the site itself that makes trying to figure out where the browser is pulling the actual data from at any given point a bit of a mess that is dependent on where and when that favicon is displayed (a menu, a toolbar, the URL bar, etc.) and whether that site has been visited recently/visited not-so-recently/visited in a past life/never visited/bookmarked/bookmarked last week/etc. As far as I know, Chrome likes to store these favicons internally as 16x16 bitmap data in all these times and places where favicons might be stored, and changing all that would probably be a buggy and painful task because other bits of code, no doubt, also depend on these data structures and bits of history to come in certain-sized chunks. For now it seems easier for Chrome/Chromium developers to pretend that favicons are a non-issue, so I wouldn't hold your breath on seeing any changes in Chrome favicons any time soon.