Range.comparePoint should throw TypeError when refNode is not an object

Range.comparePoint should throw TypeError when refNode is not an object

SPEC: http://www.w3.org/TR/WebIDL/#es-interface

A failed test case will be passed with this CL in
http://w3c-test.org/dom/ranges/Range-comparePoint-2.html

TEST=LayoutTests/fast/dom/Range/range-comparePoint.html

Behavior in other browsers.
*)FF: PASS
*)IE: PASS

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

[kangil_, 2014-07-24 07:21:08]

PTAL

[haraken, 2014-07-24 07:39:58]

LGTM, given the spec and the behavior of Firefox and IE.

[kangil_, 2014-07-24 07:52:38]

The CQ bit was checked by kangil.han@samsung.com

[commit-bot: I haz the power, 2014-07-24 07:52:52]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/kangil.han@samsung.com/410413002/1

[commit-bot: I haz the power, 2014-07-24 09:00:06]

Change committed as 178828

[sof, 2014-07-24 10:52:21]

It throws already, albeit not TypeError. Do we need both checks?

[kangil_, 2014-07-24 11:27:37]

On 2014/07/24 10:52:21, sof wrote:
> It throws already, albeit not TypeError. Do we need both checks?

Ah, my bad.
Null check should be deleted in Range::comparePoint since it is not necessary
anymore.
I will make a follow-up CL for that.
Thanks for information. :)

[kangil_, 2014-07-24 11:53:58]

On 2014/07/24 11:27:37, kangil_ wrote:
> On 2014/07/24 10:52:21, sof wrote:
> > It throws already, albeit not TypeError. Do we need both checks?
> 
> Ah, my bad.
> Null check should be deleted in Range::comparePoint since it is not necessary
> anymore.
> I will make a follow-up CL for that.
> Thanks for information. :)

Uploaded at https://codereview.chromium.org/412143007/