ChromeHTML's display name is too specific |
|||||
Issue descriptionHKCR\ChromeHTML uses "Chrome HTML document" as a display name. But ChromeHTML is Chrome's prog id and is used by all of its protocols which results in "Chrome HTML document" being displayed where it doesn't belong (see SS). I think "Google Chrome" would be better (i.e. replace BrowserDistribution::GetBrowserProgIdDesc() with BrowserDistribution::GetDisplayName()?). Otherwise what IE does is have a different HKCR entry for each of its supported file type/protocol, e.g. IE.AssocFileHTM, IE.AssocFile.MHT, ..., IE.FTP, IE.HTTP, etc. These findings came out of a discussion @ https://codereview.chromium.org/2076253002/diff/160001/chrome/browser/shell_integration_win.cc#newcode204
,
Nov 8 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 20 2017
Is there still the appetite to fix this? If so, feel free to reopen.
,
Nov 21 2017
This is still incorrect, a good first Windows bug
,
Nov 21
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by robliao@chromium.org
, Nov 7 2016Status: Available (was: Untriaged)