I think this is quite related to issue 653576. Basically, I think the right thing to do would be to register different progids for various file associations so that each could have a distinct name and icon. Or maybe just one generic "a document opened by Chrome" icon that isn't the same as Chrome's product icon.

I think it should follow the same requirements as the main product icon (theme/google_chrome/win/chrome.ico).

I don't think we should necessarily get in the habit of providing N different icons (maybe N names are fine though) since those are diminishing returns.

I think the latter is low-effort enough, with a generic chrome-document logo. I'll see if we can get document icons for these. "Chrome HTML document" has always bothered me as there's nothing Chrome-specific in the filetype itself, it's just handled by Chrome.

As this string shows up for both files and protocols like irc:// another viable string would be "Handled by Chrome", as I think it shows as "Type: Handled by Chrome". This would cover both protocol and document. Not sure if other surfaces would make this style violation blatant, and translations might not perfectly cover it either, but I think both of these would be a large improvement on the current state of things.

+gab@ FYI / if you have strong opinions on making the protocol-handler cases better. If we change the default file-association icon I believe irc:// with Chrome as a protocol handler would show a document icon.