Closed Bug 368745 Opened 19 years ago Closed 18 years ago

Use nsIFaviconService in Feed Preview

Categories

(Firefox Graveyard :: RSS Discovery and Preview, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 3 alpha5

People

(Reporter: asaf, Assigned: asaf)

References

Details

Attachments

(1 file, 1 obsolete file)

In places-builds, we should use nsIFaviconService in Feed Preview.
Attached patch v1 (obsolete) — Splinter Review
Attachment #253429 - Flags: review?(gavin.sharp)
Priority: -- → P3
Attachment #253429 - Flags: review?(sayrer)
Comment on attachment 253429 [details] [diff] [review] v1 >Index: browser/components/feeds/src/FeedWriter.js ... >+ var faviconURL = null; >+ try { >+ faviconURL = faviconsSvc.getFaviconForPage(aURI); >+ } >+ catch(ex) { } >+ >+ if (faviconURL) { Why are we swallowing all exceptions? Shouldn't we at least check for a specific error that we expect?
Attachment #253429 - Flags: review?(sayrer) → review+
Attachment #253429 - Flags: review?(gavin.sharp) → review?(sspitzer)
Comment on attachment 253429 [details] [diff] [review] v1 r=sspitzer as for robert's question, the favicon service will throw NS_ERROR_NOT_AVAILABLE when "the page is not found or it has no favicon". see also bug #381396 about the places api using NS_ERROR_NOT_AVAILABLE in this manner.
Attachment #253429 - Flags: review?(sspitzer) → review+
Attached patch as checked inSplinter Review
Attachment #253429 - Attachment is obsolete: true
mozilla/browser/components/feeds/src/FeedWriter.js 1.40
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Target Milestone: Firefox 3 alpha2 → Firefox 3 alpha5
Depends on: 398130
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: