VideoCodecProfile is brittle |
||||
Issue descriptionVideoCodecProfile combines both codec and profile into a single enum, and uses MIN/MAX ranges to allow extraction of just the codec. However, it is densely populated, so it is not possible to add profiles while maintaining the values. These values are also reported to the Media.VideoCodecProfile UMA, so they cannot change. Two paths forward: - Stop using VideoCodecProfile, always use a separate codec and profile. Note that media::MimeUtil already has a Codec enum. - Make the reporting step a mapping, so that VideoCodecProfile can be changed. We should do both.
,
Apr 21 2017
,
Apr 23 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 23 2018
Still an issue, just not a very pressing one. |
||||
►
Sign in to add a comment |
||||
Comment 1 by sheriffbot@chromium.org
, Apr 21 2017Status: Untriaged (was: Available)