nsNavHistory.cpp has some functions for finding out the effective TLD of a URL (see GetTLDType and friends). This is now available as a service, and we should switch to using that instead. We might want to use the helpers proposed in bug #367446 if/when they go in.

I'm not likely to be able to work on these bugs anytime soon.

-> me. always nice to see more etld consumers!

see http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/toolkit/components/places/src/nsNavHistory.cpp&rev=1.187#1695 and its callsites also related, http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/toolkit/components/places/src/nsNavHistory.cpp&rev=1.187#1679

switches over to the etldservice and removes unnecessary code. (note that this patch depends on bug 402008 and bug 402013, which affect the normalization semantics here.) dan, would you mind reviewing this? (if not, do you know who'd be appropriate?) thanks!

this is ready to land once it gets review (the two bugs that block this have been fixed).

Comment on attachment 287814 [details] [diff] [review] patch v1 Looks OK, and tested by hacking my build to GROUP_BY_DOMAIN in the sidebar. It is hot.

Dietrich, is a second r+ needed? You might want to take a look anyway, it's been a few months since I've really been in nsNavHistory.cpp.

Comment on attachment 287814 [details] [diff] [review] patch v1 a=mconnor on behalf of drivers. yay for no more duplication

dwitte - plan on landing this when the tree opens?

yep, for b4

FWIW, I've been using this patch + a patch to enable GROUP_BY_DOMAIN in the sidebar in my personal builds. It's very nice.

sdwilsh, dietrich - it looks like the GROUP_BY_DOMAIN functionality has been sitting around, but isn't used anywhere by default yet (comment 11) - is this something we want to enable for firefox 3? it sounds pretty cool.

checked in, with above tweak to init the eTLD and IDN services lazily, and thus avoid Ts penalty. (since this feature isn't even really used, yet...) fixed!

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