Sync the Window interface with the many specs

Sync the Window interface with the many specs

https://html.spec.whatwg.org/#the-window-object
and many other specs with partial Window interfaces.

Add UseCounters to the non-standard things that didn't already have
them, and put MeasureAs/DeprecatedAs at the beginning of each line to
make it more obvious that they are all counted.

prompt()'s second argument was left as |defaultValue|, as |default| is
a C++ keyword.

The only changes to the generated code are due to renamed arguments and
added UseCounters.

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

[philipj_slow, 2015-03-06 12:20:57]

philipj@opera.com changed reviewers:
+ haraken@chromium.org

[philipj_slow, 2015-03-06 12:20:57]

PTAL. Depends on https://codereview.chromium.org/988683002/

[haraken, 2015-03-06 12:47:58]

haraken@chromium.org changed reviewers:
+ yukishiino@chromium.org

[haraken, 2015-03-06 12:47:58]

LGTM

https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl
File Source/core/frame/Window.idl (right):

https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl...
Source/core/frame/Window.idl:40: // FIXME: document should be [Unforgeable].

shiino-san: We should add [Unforgeable] in a follow-up CL. Currently all DOM
attributes are treated as [Unforgeable] by default and we're now changing the
behavior to not-unforgeable (by moving them to prototype chains). If we miss
adding [Unforgeable] on DOM attributes that should have [Unforgeable], we'll
break a lot of things :)

[Yuki, 2015-03-06 13:30:06]

https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl
File Source/core/frame/Window.idl (right):

https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl...
Source/core/frame/Window.idl:40: // FIXME: document should be [Unforgeable].
On 2015/03/06 12:47:58, haraken wrote:
> 
> shiino-san: We should add [Unforgeable] in a follow-up CL. Currently all DOM
> attributes are treated as [Unforgeable] by default and we're now changing the
> behavior to not-unforgeable (by moving them to prototype chains). If we miss
> adding [Unforgeable] on DOM attributes that should have [Unforgeable], we'll
> break a lot of things :)

Good to know.

By the way, why don't we make document [Unforgeable] in this CL?
What's preventing us to make it [Unforgeable]?

[haraken, 2015-03-06 13:37:37]

On 2015/03/06 13:30:06, Yuki wrote:
> https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl
> File Source/core/frame/Window.idl (right):
> 
>
https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl...
> Source/core/frame/Window.idl:40: // FIXME: document should be [Unforgeable].
> On 2015/03/06 12:47:58, haraken wrote:
> > 
> > shiino-san: We should add [Unforgeable] in a follow-up CL. Currently all DOM
> > attributes are treated as [Unforgeable] by default and we're now changing
the
> > behavior to not-unforgeable (by moving them to prototype chains). If we miss
> > adding [Unforgeable] on DOM attributes that should have [Unforgeable], we'll
> > break a lot of things :)
> 
> Good to know.
> 
> By the way, why don't we make document [Unforgeable] in this CL?
> What's preventing us to make it [Unforgeable]?

Nothing prevents. We can do it in this CL, but philip's first goal is to make
existing Blink IDLs consistent with the spec, so we want to make non-trivial
changes in these efforts :)

[haraken, 2015-03-06 13:38:12]

On 2015/03/06 13:37:37, haraken wrote:
> On 2015/03/06 13:30:06, Yuki wrote:
> >
https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl
> > File Source/core/frame/Window.idl (right):
> > 
> >
>
https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl...
> > Source/core/frame/Window.idl:40: // FIXME: document should be [Unforgeable].
> > On 2015/03/06 12:47:58, haraken wrote:
> > > 
> > > shiino-san: We should add [Unforgeable] in a follow-up CL. Currently all
DOM
> > > attributes are treated as [Unforgeable] by default and we're now changing
> the
> > > behavior to not-unforgeable (by moving them to prototype chains). If we
miss
> > > adding [Unforgeable] on DOM attributes that should have [Unforgeable],
we'll
> > > break a lot of things :)
> > 
> > Good to know.
> > 
> > By the way, why don't we make document [Unforgeable] in this CL?
> > What's preventing us to make it [Unforgeable]?
> 
> Nothing prevents. We can do it in this CL, but philip's first goal is to make
> existing Blink IDLs consistent with the spec, so we want to make non-trivial
> changes in these efforts :)

s/want to make/don't want to make/

[Yuki, 2015-03-06 13:39:19]

On 2015/03/06 13:38:12, haraken wrote:
> On 2015/03/06 13:37:37, haraken wrote:
> > On 2015/03/06 13:30:06, Yuki wrote:
> > >
> https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl
> > > File Source/core/frame/Window.idl (right):
> > > 
> > >
> >
>
https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl...
> > > Source/core/frame/Window.idl:40: // FIXME: document should be
[Unforgeable].
> > > On 2015/03/06 12:47:58, haraken wrote:
> > > > 
> > > > shiino-san: We should add [Unforgeable] in a follow-up CL. Currently all
> DOM
> > > > attributes are treated as [Unforgeable] by default and we're now
changing
> > the
> > > > behavior to not-unforgeable (by moving them to prototype chains). If we
> miss
> > > > adding [Unforgeable] on DOM attributes that should have [Unforgeable],
> we'll
> > > > break a lot of things :)
> > > 
> > > Good to know.
> > > 
> > > By the way, why don't we make document [Unforgeable] in this CL?
> > > What's preventing us to make it [Unforgeable]?
> > 
> > Nothing prevents. We can do it in this CL, but philip's first goal is to
make
> > existing Blink IDLs consistent with the spec, so we want to make non-trivial
> > changes in these efforts :)
> 
> s/want to make/don't want to make/

Got it.  Please land this CL.

[philipj_slow, 2015-03-06 15:56:06]

The CQ bit was checked by philipj@opera.com

[commit-bot: I haz the power, 2015-03-06 15:57:36]

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

[philipj_slow, 2015-03-06 15:57:36]

On 2015/03/06 13:39:19, Yuki wrote:
> On 2015/03/06 13:38:12, haraken wrote:
> > On 2015/03/06 13:37:37, haraken wrote:
> > > On 2015/03/06 13:30:06, Yuki wrote:
> > > >
> >
https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl
> > > > File Source/core/frame/Window.idl (right):
> > > > 
> > > >
> > >
> >
>
https://codereview.chromium.org/984943002/diff/1/Source/core/frame/Window.idl...
> > > > Source/core/frame/Window.idl:40: // FIXME: document should be
> [Unforgeable].
> > > > On 2015/03/06 12:47:58, haraken wrote:
> > > > > 
> > > > > shiino-san: We should add [Unforgeable] in a follow-up CL. Currently
all
> > DOM
> > > > > attributes are treated as [Unforgeable] by default and we're now
> changing
> > > the
> > > > > behavior to not-unforgeable (by moving them to prototype chains). If
we
> > miss
> > > > > adding [Unforgeable] on DOM attributes that should have [Unforgeable],
> > we'll
> > > > > break a lot of things :)
> > > > 
> > > > Good to know.
> > > > 
> > > > By the way, why don't we make document [Unforgeable] in this CL?
> > > > What's preventing us to make it [Unforgeable]?
> > > 
> > > Nothing prevents. We can do it in this CL, but philip's first goal is to
> make
> > > existing Blink IDLs consistent with the spec, so we want to make
non-trivial
> > > changes in these efforts :)
> > 
> > s/want to make/don't want to make/
> 
> Got it.  Please land this CL.

Sent to CQ. I wasn't aware that [Unforgeable] was the default or I would have
tried to and included it if there were no changes to the generated code.

[philipj_slow, 2015-03-06 18:36:01]

update test

[philipj_slow, 2015-03-06 18:36:17]

The CQ bit was checked by philipj@opera.com

[philipj_slow, 2015-03-06 18:36:17]

The patchset sent to the CQ was uploaded after l-g-t-m from haraken@chromium.org
Link to the patchset: https://codereview.chromium.org/984943002/#ps20001 (title:
"update test")

[commit-bot: I haz the power, 2015-03-06 18:36:20]

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

[commit-bot: I haz the power, 2015-03-06 21:13:14]

Committed patchset #2 (id:20001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=191461