I talked to hubbe@ briefly. It seems the target color space comes from the OS and browser, not from the video or demuxer. It can change whenever user changes the device's color profile. Therefore, in most cases it seems fairly reasonable to assume the color space won't change during a playback. If we do want to handle the target color space change, a demuxer config change seems the wrong place to signal it.
With that, I wonder whether it make sense to just pass the target color space when we create our media::Renderer, or media::VideoDecoder, instead of passing it to VideoDecoder::Initialize() as part of VideoDecoderConfig.
Comment 1 by xhw...@chromium.org
, May 11 2018