Open Bug 779027 Opened 12 years ago Updated 2 months ago

Cache representative favicon colors in Places database to fill background where necessary

Categories

(Toolkit :: Places, enhancement, P5)

enhancement
Points:
8

Tracking

()

People

(Reporter: ahurle, Unassigned)

References

(Depends on 1 open bug)

Details

After the component in bug 634139 is complete, we need to cache representative favicon colors in the places database so they can be quickly displayed in the awesomebar results without repeatedly analyzing each favicon. Whenever favicon data is set on an image that is small enough that it will need to show a colored border in the results, we should analyze the favicon and update the cached representative color. Where this color should sit in the database depends on how bug 751712 turns out.
Blocks: 783339
Depends on: 818936
Whiteboard: p=0
Blocks: 784042
No longer blocks: fxdesktopbacklog
Flags: firefox-backlog+
Whiteboard: p=0 → p=8 [qa?]
Points: --- → 8
Flags: qe-verify?
Whiteboard: p=8 [qa?]
Priority: -- → P3
Severity: normal → S3

Changing qe-verify? to qe-verify+.

Flags: qe-verify? → qe-verify+

ColorAnalyzer was removed in bug 1525100. Should this bug be closed?

Flags: needinfo?(mak)

I think it may still be a useful enhancement in the future, ColorAnalyzer may be reintroduced or improved through a ML model.
I don't think it's a short term requirement anyway.

Severity: S3 → N/A
Type: defect → enhancement
Flags: needinfo?(mak)
Priority: P3 → P5
Summary: Cache representative favicon colors in Places database → Cache representative favicon colors in Places database to fill background where necessary
You need to log in before you can comment on or make changes to this bug.