PPAPI: Remove whitelist checks for PPB_VideoDecoder now that it's stable.

PPAPI: Remove whitelist checks for PPB_VideoDecoder now that it's stable.
Whitelist checks prevent most clients from successfully creating a video
decoder resource. Remove the whitelist checks now that the API is stable.

BUG=447741
Committed: https://crrev.com/622cde4e3d0fce0d8b3cd2b4bb0207a472229ea5
Cr-Commit-Position: refs/heads/master@{#310911}

[bbudge, 2015-01-09 21:39:51]

bbudge@chromium.org changed reviewers:
+ dmichael@chromium.org

[bbudge, 2015-01-09 21:44:05]

bbudge@chromium.org changed reviewers:
+ jam@chromium.org, thakis@chromium.org

[bbudge, 2015-01-09 21:44:05]

+jam for content/
+thakis for chrome/

[dmichael (off chromium), 2015-01-09 21:49:41]

lgtm

[bbudge, 2015-01-09 22:45:02]

bbudge@chromium.org changed reviewers:
+ scottmg@chromium.org

[bbudge, 2015-01-09 22:45:03]

+scottmg for chrome/ and content/

[scottmg, 2015-01-09 22:55:10]

On 2015/01/09 22:45:03, bbudge wrote:
> +scottmg for chrome/ and content/

Did you mean sky? I don't think I OWNERS anything here.

[bbudge, 2015-01-09 22:58:55]

On 2015/01/09 22:55:10, scottmg wrote:
> On 2015/01/09 22:45:03, bbudge wrote:
> > +scottmg for chrome/ and content/
> 
> Did you mean sky? I don't think I OWNERS anything here.

Whoops, sorry Scott.

[bbudge, 2015-01-09 23:01:44]

bbudge@chromium.org changed reviewers:
+ piman@chromium.org
- jam@chromium.org

[bbudge, 2015-01-09 23:01:44]

-jam
+piman for content/

[bbudge, 2015-01-09 23:03:44]

bbudge@chromium.org changed reviewers:
+ avi@chromium.org
- piman@chromium.org

[bbudge, 2015-01-09 23:03:44]

-piman
+avi for content/

[Avi (use Gerrit), 2015-01-09 23:07:08]

LGTM

https://codereview.chromium.org/845823002/diff/20001/content/renderer/pepper/...
File content/renderer/pepper/content_renderer_pepper_host_factory.cc (right):

https://codereview.chromium.org/845823002/diff/20001/content/renderer/pepper/...
content/renderer/pepper/content_renderer_pepper_host_factory.cc:164: }
To match the style of the surrounding code, drop the now-extraneous braces.

[Nico, 2015-01-09 23:08:05]

chrome lgtm

Hooray!

[bbudge, 2015-01-09 23:22:04]

https://codereview.chromium.org/845823002/diff/20001/content/renderer/pepper/...
File content/renderer/pepper/content_renderer_pepper_host_factory.cc (right):

https://codereview.chromium.org/845823002/diff/20001/content/renderer/pepper/...
content/renderer/pepper/content_renderer_pepper_host_factory.cc:164: }
On 2015/01/09 23:07:08, Avi wrote:
> To match the style of the surrounding code, drop the now-extraneous braces.

Good eye. Done!

[bbudge, 2015-01-09 23:25:17]

The CQ bit was checked by bbudge@chromium.org

[commit-bot: I haz the power, 2015-01-09 23:26:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/845823002/40001

[piman, 2015-01-09 23:32:51]

piman@chromium.org changed reviewers:
+ piman@chromium.org

[piman, 2015-01-09 23:32:52]

LGTM+++

[scottmg, 2015-01-09 23:36:21]

(s/not/now/ in description if that doesn't require restarting cq, and lgtm for
what that's worth)

[bbudge, 2015-01-09 23:40:01]

Thanks for quick reviews everyone.
Scott, if it's OK with you I'll fix the description after landing.

[commit-bot: I haz the power, 2015-01-10 00:27:48]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-01-10 00:28:39]

Patchset 3 (id:??) landed as
https://crrev.com/622cde4e3d0fce0d8b3cd2b4bb0207a472229ea5
Cr-Commit-Position: refs/heads/master@{#310911}

[Nico, 2015-01-10 00:43:47]

On 2015/01/09 23:40:01, bbudge wrote:
> Thanks for quick reviews everyone.
> Scott, if it's OK with you I'll fix the description after landing.

FYI, you can just edit the cl description on rietveld and land. This should take
2 seconds, won't invalidate try results, and makes sure that the fixed
description appears in `git log`. So there never should be a reason to delay cl
description fixes.

[bbudge, 2015-01-10 00:45:47]

On 2015/01/10 00:43:47, Nico wrote:
> On 2015/01/09 23:40:01, bbudge wrote:
> > Thanks for quick reviews everyone.
> > Scott, if it's OK with you I'll fix the description after landing.
> 
> FYI, you can just edit the cl description on rietveld and land. This should
take
> 2 seconds, won't invalidate try results, and makes sure that the fixed
> description appears in `git log`. So there never should be a reason to delay
cl
> description fixes.

Thanks, I didn't know that.