Favicon is not displayed for NTP after killing the page.
Reported by
vku...@etouch.net,
Sep 13 2016
|
||||||
Issue descriptionChrome Version:55.0.2859.0 3f63c614e8c4501b1bfa3f608e32a9d12618b0a0-refs/heads/master@{#418117} (32/64-bit) OS:Windows (7,8,8.1,10),Linux (14.04 LTS) What steps will reproduce the problem? (1)Launch chrome and open 2 NTP (2)Crash the page of 1 NTP manually via chrome://kill and observe favicon of both NTP's Actual: Favicon is not displayed for NTP after killing the page. Expected: Favicon should be displayed for both NTP after killing the page. This is a Non-regression issue seen from 'M30' series i.e from build 30.0.1549.1 Note: Issue not seen on Mac OS.
,
Sep 13 2016
,
Aug 2 2017
Pri 3 issues don't need (obsolete) target milestones.
,
Aug 2
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
,
Sep 16
+Yana: Is this WAI? The behavior is the same on all 4 desktop platforms - the killed NTP gets an updated favicon; other NTPs get the same "Aw, Snap!" content update, but don't get a favicon update. BTW: If we think this should be updated, it belongs in a different component (perhaps TabStrip?_.
,
Sep 17
CC'ing Will for his opinion since we worked on the saddest of tabs together. I think it's not worth fixing this. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ranjitkan@chromium.org
, Sep 13 2016