WebContents currently forwards the favicon URL to chrome code that will handle the download of the favicon. Do we want to replicate a similar mechanism in the content service? Should we look to generalize the concept instead, and just provide a stream that will contain icon data, regardless of the actual mechanism for obtaining it?