Added InvalidAccessError exception

Added InvalidAccessError exception

Platform support for this exception is missing and is needed in order
to be compliant with Clearkey tests of Youtube's MSE/EME conformance suite.

Test suite: http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/main.html

BUG=

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=162364

[abarth-chromium, 2013-11-15 16:00:23]

Does this CL have an observable effects?  If not, we should probably wait until
we can land enough code to have an observable effect.  If it does, we should
write a test that demonstrates the effects.

[landell, 2013-11-18 08:10:04]

On 2013/11/15 16:00:23, abarth wrote:
> Does this CL have an observable effects?  If not, we should probably wait
until
> we can land enough code to have an observable effect.  If it does, we should
> write a test that demonstrates the effects.

It will not have any observable effects unless the WebMediaPlayer implementation
is actually using this. Our implementation of that interface is using this,
obviously. The failing test case of the tip of YT's conformance suite is
CKAddKey (test 68) which is also failing on Chrome unstable. Note that the test
suite is constantly moving so the test name and number might change.

[xhwang, 2013-11-18 17:17:13]

On 2013/11/18 08:10:04, landell wrote:
> On 2013/11/15 16:00:23, abarth wrote:
> > Does this CL have an observable effects?  If not, we should probably wait
> until
> > we can land enough code to have an observable effect.  If it does, we should
> > write a test that demonstrates the effects.
> 
> It will not have any observable effects unless the WebMediaPlayer
implementation
> is actually using this. Our implementation of that interface is using this,
> obviously. The failing test case of the tip of YT's conformance suite is
> CKAddKey (test 68) which is also failing on Chrome unstable. Note that the
test
> suite is constantly moving so the test name and number might change.

The failing CKAddKey test is tracked by crbug.com/312820

[abarth-chromium, 2013-11-18 17:50:23]

LGTM, assuming we plan to run the conformance tests automatically.

[landell, 2013-11-19 08:59:34]

Since this is my first chromium patch I am a bit unsure about the procedures.
Shall I do anything more now or will this patch be integrated in due time?

[Mostyn Bramley-Moore, 2013-11-19 09:11:54]

> The failing CKAddKey test is tracked by crbug.com/312820

Can you give us access to view that issue?  I get a "Your client does not have
permission to get URL"/403 error.

[Daniel Bratell, 2013-11-19 10:30:55]

On 2013/11/19 08:59:34, landell wrote:
> Since this is my first chromium patch I am a bit unsure about the procedures.
> Shall I do anything more now or will this patch be integrated in due time?

You check the "Commit" checkbox above (no feedback except for the checkbox being
ticked). Then you wait for the commitqueue (cq) bot to notice and start the
process. If all tests pass it will be integrated.

[commit-bot: I haz the power, 2013-11-19 10:42:06]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/landell@opera.com/62543003/1

[commit-bot: I haz the power, 2013-11-19 11:19:11]

Retried try job too often on linux_blink for step(s) blink_platform_unittests,
webkit_lint, webkit_python_tests, webkit_tests, webkit_unit_tests, wtf_unittests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_blin...

[landell, 2013-11-20 08:59:37]

Since the changes introduced in the rebase are trivial I assume the LGTM is
still valid so retrying the commit.

[commit-bot: I haz the power, 2013-11-20 11:26:32]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/landell@opera.com/62543003/100002

[commit-bot: I haz the power, 2013-11-20 13:38:51]

Change committed as 162364