Open Bug 323933 Opened 19 years ago Updated 2 years ago

Set site favicons for domain/host groups

Categories

(Firefox :: Bookmarks & History, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: brettw, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: polish, Whiteboard: [polish-hard][polish-visual][icon-namoroka][polish-p3])

When we have results and "most" of the pages in a domain or host group have the same favicon, that host group should get that favicon and it should appear in the tree view. I did a quick mockup and this looks a lot better when you see a list of hosts, since it makes it easier to pick out the one you want.
Priority: -- → P5
Target Milestone: --- → Firefox 2 beta1
Target Milestone: Firefox 2 beta1 → Firefox 3
Assignee: brettw → nobody
Target Milestone: Firefox 3 → ---
Severity: normal → enhancement
Keywords: polish
Whiteboard: [polish-hard]
Is this still valid? Can someone with more insight into this issue post a screenshot of the problem ui element?
Assignee: nobody → ddahl
it is still valid, practically when in the sidebar you group by site (or date and site) the icon instead of being a generic folder icon, should be the most used favicon into that group, so for example if i have 10 pages from www.mozilla.com, the icon for mozilla.com container should be the dino, not a generic folder.

I was thinking we could change the query for the group to select a favicon, and make so that site containers take the default folder icon only if they don't have one set.
(In reply to comment #2)
> it is still valid, practically when in the sidebar you group by site (or date
> and site) the icon instead of being a generic folder icon, should be the most
> used favicon into that group, so for example if i have 10 pages from
> www.mozilla.com, the icon for mozilla.com container should be the dino, not a
> generic folder.

From my comment (bug 394987 comment #8)
> I would expect to do something like:
> o If there is only one page in the folder use its icon
> o If all pages in folder have same icon then use that.
> o For site.example.com, if http://site.example.com/ is in the database then use
>   its icon (possibly including other common home pages index.htm/php/shtml/html)
> o If there is a majority count for an icon for all entries in the folder (that
>   have an icon) then use that.

The only difference being step 3; However majority - which covers all the other steps - should be sufficient and easier.
Whiteboard: [polish-hard] → [polish-hard] [icons-3.2]
Whiteboard: [polish-hard] [icons-3.2] → [polish-hard] [icon-3.2]
P3 - Polish issue that is in a secondary interface, occasionally encountered, or is not easily identifiable.

The only thing that makes this not easily identifiable is that user's are probably accustomed to seeing a folder icon to represent a web site (kind of a strange extension of the desktop metaphor).  I think people would really appreciate this once it landed, assuming they take advantage of the secondary interfaces where this appears.
Whiteboard: [polish-hard] [icon-3.2] → [polish-hard] [icon-namoroka]
Priority: P5 → P3
Priority: P3 → P5
Whiteboard: [polish-hard] [icon-namoroka] → [polish-hard][polish-visual][icon-namoroka][polish-p3]
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".

In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body   contains   places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.

Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.

Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
Assignee: ddahl → nobody
Priority: P5 → --
Priority: -- → P3

Some time ago, Gijs suggested marking the last stored icon for a domain as a "fallback" icon.

Depends on: 1664001
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.