Make Range constructable

Make Range constructable

http://dom.spec.whatwg.org/#interface-range

Now we can do `new Range()` instead of `document.createRange()`.

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

[Julie Parent, 2013-05-03 21:50:38]

Maybe worth adding a test in a multi-document setting to ensure that the correct
document is used to construct the range?

[eseidel, 2013-05-04 01:20:42]

Does HTML5 say this is OK?

I like this.  But I don't want this to be blink-only.

[eseidel, 2013-05-04 01:29:07]

lgtm

Sorry, I missed the spec link.  So what's the story with other browsers?  This
seems trivial.  So long there isn't a browser mob with pitchforks, I think we
should do this.

[arv (Not doing code reviews), 2013-05-06 14:15:32]

On 2013/05/04 01:29:07, Eric Seidel (Google) wrote:
> lgtm
> 
> Sorry, I missed the spec link.  So what's the story with other browsers?  This
> seems trivial.  So long there isn't a browser mob with pitchforks, I think we
> should do this.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14141

It has been a general consensus for a while now that we want to make "all" DOM
interfaces constructable.

I'll make sure I'll file Gecko and WebKit bugs.

[commit-bot: I haz the power, 2013-05-06 20:58:19]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/arv@chromium.org/14904005/11001

[commit-bot: I haz the power, 2013-05-06 21:00:42]

Change committed as 149794