All image_fetcher and image_decoder related code should live in the component directory.
Currently e.g. the platform dependent image decoders implementations live in
//chrome/browser/search/suggestions/ and
//ios/chrome/browser/suggestions/
Actually I don't think so. The non-ios implementation uses chrome/browser/image_decoder.h, so it can't move into the component. Not sure about the ios one.
They definitely should move out of /suggestions though.
The iOS one can be moved easily because it does not have a dependency on chrome/browser/.
Bummer I forgot about this the image_decoder. :-(
I will still continue to investigate.
Right, that should be possible! It'll be a bit of work though to pull the other dependencies on chrome/ out of the image decoder. Not sure it's worth the effort and churn (but up to you :) ).
I think dependencies on content/ from components/ also need some special care?
Comment 1 by treib@chromium.org
, Jun 30 2016