Is there an intentional difference between |ResourceBundle::GetNativeImageNamed| and |ResourceBundle::GetImageNamed|?
If so, can we document this somewhere (preferably in the code)?
When working on CLs [1] loading PNGs into the FaviconService,
we used |ResourceBundle::GetImageNamed| to load the added resources.
Instead of the images, we received a small yellow image as response.
We used |ResourceBundle::GetNativeImageNamed| to have it working as intended.
There is no clue that those function might work differently and the expected behavior would be that both behave in a similar way.
[1] Patchset with unexpected behavior:
https://codereview.chromium.org/2695713004/#ps120001
Change icon_cacher_impl.cc to use GetNativeImageNamed and all icons will appear.
In order to see the effect, be offline when starting Chrome for the first time. If it works, you see images. If it doesn't there will be yellow tiles (background inferred from unsuitable image).
Comment 1 by sheriffbot@chromium.org
, Feb 21 2018Status: Untriaged (was: Available)