New issue
Advanced search Search tips

Issue 593076 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 461009
Owner: ----
Closed: Mar 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Use MimeUtil::Codec enum values instead of strings for container format-to-codec mapping

Project Member Reported by ddorwin@chromium.org, Mar 8 2016

Issue description

Currently, kFormatCodecMappings maps a container name to a string containing a comma-separated list of codec strings. This is confusing since it appears all codec strings are listed and involves unnecessary processing of the strings to determine the corresponding MimeUtil::Codec enum value. It can also lead to confusion, such as that some values are allowed while other are not (e.g.  issue 589675 ).

It would be better to start with a list of MimeUtil::Codec enum values.
 
Mergedinto: 461009
Status: Duplicate (was: Available)

Sign in to add a comment