Favicons, Favicon Picker
Starting with version 0.3.3.0, LiveClick includes limited support for changing Live Bookmark favicons with Favicon Picker 3 (version 0.5), but there’s a small bug in Favicon Picker that needs to be addressed first. I’ve emailed the developer of Favicon Picker 3, so hopefully we’ll be able to sort that out.
If you feel comfortable navigating your Firefox profile and editing JavaScript files, you can make the necessary changes without waiting for an update from Favicon Picker 3. First, find Favicon Picker 3’s chrome content directory on your computer (tip: the extension ID is 446c03e0-2c35-11db-a98b-0800200c9a67) and open faviconpicker.js with your text editor of choice.
Set the bookmark variable (Line 9) to an empty string:
bookmark: "",
Then, add these lines to the top of the init function (Line 18):
try
{
this.bookmark = PlacesUtils.bookmarks.getBookmarkURI(window.arguments[0].itemId);
}
catch (e) {}
if (this.bookmark == "") return;
Save. Restart Firefox and open up the properties of any Live Bookmark. You should be able to “Browse” and change the favicon. You might have to reload the Live Bookmark or restart Firefox to force the new favicons to appear.
One other note: using Favicon Picker’s “Reset” and “Blank” buttons with Live Bookmarks probably won’t work as expected. Still working on that.
In a separate, but similar issue, many have noted that you can’t permanently change the “Site Location” of Live Bookmarks. Consequently, changing the “Site Location” to get the correct favicon of a Live Bookmark won’t work because Firefox will always revert back to the original location and favicon.
This is a side effect of Bug 341972. I’ve also debated the change in a separate bug (albeit poorly). Rest assured, I’ll continue to search for a solution to this. Thanks for your patience.
Posted on Mar 17 2009 at 03:57 PM
Next entry: LiveClick 0.3.4.0
Previous entry: LiveClick 0.3.3.0
Quick note: If you’re trying to get Favicon Picker working with LiveClick, I’d recommend updating to LiveClick 0.3.4.0. The update contains another bug that might be causing some problems.
If you still have problems, let me know and I’ll try to walk you through it.
Posted by protejohnny on 03/18 at 05:25 PM
Thanks for the great workaround protejohnny. Got it working fine.
Posted by Matt de Neef on 06/20 at 09:43 PM
Hi, I can’t get this to work unfortunately. Is there any chance you could upload the working, modified .js file for us, or maybe email it to me? Thanks.
Posted by jimbo81 on 03/18 at 01:20 PM