Closed Bug 649347 Opened 14 years ago Closed 14 years ago

about: pages do not have favicons on the thumbnails

Categories

(Firefox Graveyard :: Panorama, defect)

defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED
Firefox 6

People

(Reporter: AlexLakatos, Assigned: raymondlee)

References

Details

Attachments

(2 files, 3 obsolete files)

Attached image screenshot
about: pages (about:home, about:robots) do not have favicons on the thumbnails in Panorama, even if in Tab View they have. Steps to Reproduce: 1.Open about:home 2.Enter Panorama View Actual Results: 2.The thumbnail showing about:home does not have a favicon on it Expected Results 2.2.The thumbnail showing about:home has a favicon on it
Depends on: 627966
I can confirm. It appears to be this way for any page that does not have a favicon associated with it (?)
No, any other page without a favicon has a "white page" as its favicon in Panorama.
Attached patch v1 (obsolete) — Splinter Review
Assignee: nobody → raymond
Status: NEW → ASSIGNED
Attachment #526699 - Flags: feedback?(tim.taubert)
Attachment #526699 - Attachment is patch: true
Attachment #526699 - Attachment mime type: application/octet-stream → text/plain
Comment on attachment 526699 [details] [diff] [review] v1 I just tried this patch and it works for "about:home" but not for "about:robots" (maybe this one is special because the icon is an animated PNG and embedded as a base64 string). These both have no favicon when they're pinned.
Attachment #526699 - Flags: feedback?(tim.taubert) → feedback-
Attached patch v2 (obsolete) — Splinter Review
Please apply the patch for bug 627966 and the this patch
Attachment #526699 - Attachment is obsolete: true
Attachment #527034 - Flags: feedback?(tim.taubert)
Version: unspecified → Trunk
Comment on attachment 527034 [details] [diff] [review] v2 The overall approach looks good but we should clean up the code and remove code duplicates: >diff --git a/browser/base/content/tabview/groupitems.js b/browser/base/content/tabview/groupitems.js >+ let browser = xulTab.linkedBrowser; >+ let iconUrl; >+ if (gBrowser.shouldLoadFavIcon(browser.contentDocument.documentURIObject) || >+ browser.currentURI.schemeIs("about")) { >+ if (xulTab.image) { >+ iconUrl = xulTab.image; >+ if (/^https?:/.test(iconUrl)) >+ iconUrl = "moz-anno:favicon:" + iconUrl; >+ } else { >+ iconUrl = gFavIconService.getFaviconImageForPage(browser.currentURI).spec; >+ } >+ } else { >+ iconUrl = Utils.defaultFaviconURL; >+ } >@@ -2034,18 +2046,30 @@ let GroupItems = { >+ let browser = xulTab.linkedBrowser; >+ let iconUrl; >+ if (gBrowser.shouldLoadFavIcon(browser.contentDocument.documentURIObject) || >+ browser.currentURI.schemeIs("about")) { >+ if (xulTab.image) { >+ iconUrl = xulTab.image; >+ if (/^https?:/.test(iconUrl)) >+ iconUrl = "moz-anno:favicon:" + iconUrl; >+ } else { >+ iconUrl = gFavIconService.getFaviconImageForPage(browser.currentURI).spec; >+ } >+ } else { >+ iconUrl = Utils.defaultFaviconURL; >+ } These two places do exactly the same, don't they? Let's merge them into one function. The if-condition looks pretty similar to what TabItem.shouldLoadFavicon() does - so shouldn't we rather use this function instead of duplicating the code here? >diff --git a/browser/base/content/tabview/tabitems.js b/browser/base/content/tabview/tabitems.js >+ let iconUrl; >+ if (tab.image) { >+ iconUrl = tab.image; >+ if (/^https?:/.test(iconUrl)) >+ iconUrl = "moz-anno:favicon:" + iconUrl; >+ } else { >+ iconUrl = >+ gFavIconService.getFaviconImageForPage(tab.linkedBrowser.currentURI).spec; >+ } This looks a bit like the two diffs above, maybe this could be merged into this function, too? F+ with those issues addressed.
Attachment #527034 - Flags: feedback?(tim.taubert) → feedback+
Attached patch v3 (obsolete) — Splinter Review
Merged some duplicate code
Attachment #527034 - Attachment is obsolete: true
Attachment #527462 - Flags: review?(ian)
Attachment #527462 - Flags: review?(ian) → review+
Please land this after bug 627966 has landed
Attachment #527462 - Attachment is obsolete: true
Keywords: checkin-needed
Keywords: checkin-needed
Whiteboard: [fixed-in-cedar]
Target Milestone: --- → Firefox 6
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Flags: in-testsuite?
Resolution: --- → FIXED
Whiteboard: [fixed-in-cedar]
Verified Fixed on: Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110509 Firefox/6.0a1
Status: RESOLVED → VERIFIED
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: