Some address book interfaces are read-only or limited to fields that don't support remote images or html preference fields. We should find a way around this, maybe even have a wrapper/cache around the read-only address books that lets us save extra fields like these.

This is still an issue (2 years later). I don't see that it needs a wrapper around the address book - seems like a lot of work with the potential for errors. Why not just have the "Personal Address Book" read before the "Mac OS X Address Book" and if a match is found for displaying remote content - stop there and display the content? Seems like that would take very little time to implement.

Wouldn't this be fixed by bug 457296?

(In reply to Jim Porter (:squib) from comment #2) > Wouldn't this be fixed by bug 457296? Yes, it would. Thank you for pointing me in that direction.

Or - allow us to set a global "Allows allow remote images" on the addressbook. (that's also what a filter could also be used for, except there is no fiter option for this - and that is the topic of bug #249191 )

Remote content is not in address books anymore, bug 457296 landed. -> WFM