Mark android supports H264 main/high profile

Mark android supports H264 main/high profile

Most hardware OEMs provides codecs to support H264 main/high profile.
The current way of declaring them as unsupported is too restrictive.

BUG=407741
Committed: https://crrev.com/d9b32ee803870c87f65351766e5a731f41172299
Cr-Commit-Position: refs/heads/master@{#292395}

[qinmin, 2014-08-26 21:20:31]

qinmin@chromium.org changed reviewers:
+ acolwell@chromium.org, mmenke@chromium.org

[qinmin, 2014-08-26 21:20:31]

PTAL

[acolwell GONE FROM CHROMIUM, 2014-08-26 22:38:50]

lgtm. You might want to double check to make sure that this doesn't end up
causing the canPlayType() browser tests to fail.

https://codereview.chromium.org/506283002/diff/1/net/base/mime_util.cc
File net/base/mime_util.cc (right):

https://codereview.chromium.org/506283002/diff/1/net/base/mime_util.cc#newcod...
net/base/mime_util.cc:475: // Most OEMs have their own codecs that supports
H.264 main and high
nit: Comment probably not necessary since we don't say anything about the other
codecs.

[qinmin, 2014-08-27 00:26:41]

run the content_browsertests on android, and seems it works fine.

https://codereview.chromium.org/506283002/diff/1/net/base/mime_util.cc
File net/base/mime_util.cc (right):

https://codereview.chromium.org/506283002/diff/1/net/base/mime_util.cc#newcod...
net/base/mime_util.cc:475: // Most OEMs have their own codecs that supports
H.264 main and high
On 2014/08/26 22:38:50, acolwell wrote:
> nit: Comment probably not necessary since we don't say anything about the
other
> codecs.

Done.

[mmenke, 2014-08-27 14:30:19]

On 2014/08/27 00:26:41, qinmin wrote:
> run the content_browsertests on android, and seems it works fine.
> 
> https://codereview.chromium.org/506283002/diff/1/net/base/mime_util.cc
> File net/base/mime_util.cc (right):
> 
>
https://codereview.chromium.org/506283002/diff/1/net/base/mime_util.cc#newcod...
> net/base/mime_util.cc:475: // Most OEMs have their own codecs that supports
> H.264 main and high
> On 2014/08/26 22:38:50, acolwell wrote:
> > nit: Comment probably not necessary since we don't say anything about the
> other
> > codecs.
> 
> Done.

LGTM (Though it makes me sad that net/ has to know or are about this

[qinmin, 2014-08-27 15:58:07]

The CQ bit was checked by qinmin@chromium.org

[qinmin, 2014-08-27 15:58:46]

The CQ bit was unchecked by qinmin@chromium.org

[xhwang, 2014-08-28 04:06:23]

On 2014/08/27 15:58:46, qinmin wrote:
> The CQ bit was unchecked by mailto:qinmin@chromium.org

Can we add more tests to cover H264 MAIN/HIGH profiles? e.g. 'video/mp4;
codecs="avc1.4D4041"'

[qinmin, 2014-08-28 14:19:35]

The CQ bit was checked by qinmin@chromium.org

[commit-bot: I haz the power, 2014-08-28 14:20:55]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/qinmin@chromium.org/506283002/20001

[commit-bot: I haz the power, 2014-08-28 15:44:16]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[commit-bot: I haz the power, 2014-08-28 16:17:45]

Committed patchset #2 (id:20001) as ced009f2a773ceec4f3305a97e22733dbfb685f1

[commit-bot: I haz the power, 2014-09-10 03:00:00]

Patchset 2 (id:??) landed as
https://crrev.com/d9b32ee803870c87f65351766e5a731f41172299
Cr-Commit-Position: refs/heads/master@{#292395}