Test type of exposed AnimationEffectTimingReadOnly

Test type of exposed AnimationEffectTimingReadOnly

The KeyframeEffectReadOnly interface was implemented in
https://codereview.chromium.org/2369833002 as a simple redirection to a
KeyframeEffect object (where KeyframeEffect is actually a subclass of
KeyframeEffectReadOnly).

In a subsequent patch (https://codereview.chromium.org/2379863003), the timing
attribute of KeyframeEffect was changed: KeyframeEffectReadOnly.timing is
an AnimationEffectTimingReadOnly, and KeyframeEffect.timing is an
AnimationEffectTiming (a subclass of AnimationEffectTimingReadOnly).

It turns out that if you construct a KeyframeEffectReadOnly object in
JavaScript, the V8/JavaScript interface magically interprets and represents the
underlying KeyframeEffect object as a KeyframeEffectReadOnly object, as we
wanted. But when the JavaScript then accesses the timing attribute, it appears
to treat it as a KeyframeEffect object, calling the KeyframeEffect version of
the getter instead of the KeyframeEffectReadOnly version.

This patch commits a test that illustrates the bug. A future patch will fix the
bug by actually constructing KeyframeEffectReadOnly objects in the C++.

BUG=624639
Committed: https://crrev.com/b6d80c681fbc035f6267353b4fefbab1b33744ae
Cr-Commit-Position: refs/heads/master@{#423115}

[suzyh_UTC10 (ex-contributor), 2016-10-05 07:20:00]

suzyh@chromium.org changed reviewers:
+ alancutter@chromium.org

[suzyh_UTC10 (ex-contributor), 2016-10-05 07:20:13]

Let's get this in while I work on the fix.

[alancutter (OOO until 2018), 2016-10-05 07:28:50]

lgtm

[suzyh_UTC10 (ex-contributor), 2016-10-05 07:39:16]

The CQ bit was checked by suzyh@chromium.org

[commit-bot: I haz the power, 2016-10-05 07:39:25]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-05 08:35:41]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-05 08:36:58]

Description was changed from

==========
Test type of exposed AnimationEffectTimingReadOnly

The KeyframeEffectReadOnly interface was implemented in
https://codereview.chromium.org/2369833002 as a simple redirection to a
KeyframeEffect object (where KeyframeEffect is actually a subclass of
KeyframeEffectReadOnly).

In a subsequent patch (https://codereview.chromium.org/2379863003), the timing
attribute of KeyframeEffect was changed: KeyframeEffectReadOnly.timing is
an AnimationEffectTimingReadOnly, and KeyframeEffect.timing is an
AnimationEffectTiming (a subclass of AnimationEffectTimingReadOnly).

It turns out that if you construct a KeyframeEffectReadOnly object in
JavaScript, the V8/JavaScript interface magically interprets and represents the
underlying KeyframeEffect object as a KeyframeEffectReadOnly object, as we
wanted. But when the JavaScript then accesses the timing attribute, it appears
to treat it as a KeyframeEffect object, calling the KeyframeEffect version of
the getter instead of the KeyframeEffectReadOnly version.

This patch commits a test that illustrates the bug. A future patch will fix the
bug by actually constructing KeyframeEffectReadOnly objects in the C++.

BUG=624639
==========

to

==========
Test type of exposed AnimationEffectTimingReadOnly

The KeyframeEffectReadOnly interface was implemented in
https://codereview.chromium.org/2369833002 as a simple redirection to a
KeyframeEffect object (where KeyframeEffect is actually a subclass of
KeyframeEffectReadOnly).

In a subsequent patch (https://codereview.chromium.org/2379863003), the timing
attribute of KeyframeEffect was changed: KeyframeEffectReadOnly.timing is
an AnimationEffectTimingReadOnly, and KeyframeEffect.timing is an
AnimationEffectTiming (a subclass of AnimationEffectTimingReadOnly).

It turns out that if you construct a KeyframeEffectReadOnly object in
JavaScript, the V8/JavaScript interface magically interprets and represents the
underlying KeyframeEffect object as a KeyframeEffectReadOnly object, as we
wanted. But when the JavaScript then accesses the timing attribute, it appears
to treat it as a KeyframeEffect object, calling the KeyframeEffect version of
the getter instead of the KeyframeEffectReadOnly version.

This patch commits a test that illustrates the bug. A future patch will fix the
bug by actually constructing KeyframeEffectReadOnly objects in the C++.

BUG=624639

Committed: https://crrev.com/b6d80c681fbc035f6267353b4fefbab1b33744ae
Cr-Commit-Position: refs/heads/master@{#423115}
==========

[commit-bot: I haz the power, 2016-10-05 08:36:59]

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