Make event.composedPath() on window behave the same way as that on document

Make event.composedPath() on window behave the same way as that on document

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath() on
window.

The current Blink's implementation of event.composedPath() on window returns
just [window]. Now, event.composedPath() on window behaves the same way as that on document.

BUG=645527
Committed: https://crrev.com/92dd0aa2f5587f380f7f8f7c58d1f9a9862e3254
Cr-Commit-Position: refs/heads/master@{#422368}

[hayato, 2016-09-16 11:06:07]

The CQ bit was checked by hayato@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-16 11:06:14]

Dry run: 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-09-16 12:28:20]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-16 12:28:21]

Dry run: This issue passed the CQ dry run.

[hayato, 2016-10-03 01:22:36]

Description was changed from

==========
Make the behavior of event.composedPath() on window be same to that on document

BUG=645527
==========

to

==========
Make event.composedPath() return non-empty event path on window

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath on
window.

Now, event.composedPath() on window behaves the same way as that on document.


BUG=645527
==========

[hayato, 2016-10-03 01:36:38]

rebased

[hayato, 2016-10-03 01:36:40]

The CQ bit was checked by hayato@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-03 01:36:50]

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

[hayato, 2016-10-03 01:37:17]

Description was changed from

==========
Make event.composedPath() return non-empty event path on window

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath on
window.

Now, event.composedPath() on window behaves the same way as that on document.


BUG=645527
==========

to

==========
Make event.composedPath() return non-empty event path on window

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath()
on
window.

Now, event.composedPath() on window behaves the same way as that on document.

BUG=645527
==========

[hayato, 2016-10-03 01:41:01]

hayato@chromium.org changed reviewers:
+ ojan@chromium.org, tkent@chromium.org

[hayato, 2016-10-03 01:41:01]

PTAL.

I will send a PSA to blink-dev because this is a web facing change.

[tkent, 2016-10-03 01:57:30]

Do other browsers have composedPath()? How does it work on Window?

[hayato, 2016-10-03 02:20:39]

Description was changed from

==========
Make event.composedPath() return non-empty event path on window

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath()
on
window.

Now, event.composedPath() on window behaves the same way as that on document.

BUG=645527
==========

to

==========
Make event.composedPath() on window behaves the same way as that on document

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath()
on
window.

The current Blink's implementation of event.composedPath() on window returns
just [window]. Now, event.composedPath() on window behaves the same way as that
on document.

BUG=645527
==========

[hayato, 2016-10-03 02:27:21]

On 2016/10/03 at 01:57:30, tkent wrote:
> Do other browsers have composedPath()? How does it work on Window?

Only Safari 10 shipped it. As far as I confirmed, Safari 10 returns [] (empty)
in this case, while Blink returns [window] (without this CL).
Both Blink and WebKit have to update their implementations to match the latest
DOM Standard, which I have updated recently.

[hayato, 2016-10-03 02:28:08]

Description was changed from

==========
Make event.composedPath() on window behaves the same way as that on document

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath()
on
window.

The current Blink's implementation of event.composedPath() on window returns
just [window]. Now, event.composedPath() on window behaves the same way as that
on document.

BUG=645527
==========

to

==========
Make event.composedPath() on window behave the same way as that on document

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath()
on
window.

The current Blink's implementation of event.composedPath() on window returns
just [window]. Now, event.composedPath() on window behaves the same way as that
on document.

BUG=645527
==========

[commit-bot: I haz the power, 2016-10-03 03:00:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-03 03:00:24]

Dry run: This issue passed the CQ dry run.

[tkent, 2016-10-03 03:19:03]

ok, lgtm. This CL won't increase compatibility risk.
I think only chromestatus.com entry is necessary.

[hayato, 2016-10-03 03:58:54]

Thanks. I have added an entry:
https://www.chromestatus.com/feature/4661261711179776

[hayato, 2016-10-03 03:58:59]

The CQ bit was checked by hayato@chromium.org

[commit-bot: I haz the power, 2016-10-03 03:59:13]

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-03 04:04:06]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-10-03 04:06:23]

Description was changed from

==========
Make event.composedPath() on window behave the same way as that on document

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath()
on
window.

The current Blink's implementation of event.composedPath() on window returns
just [window]. Now, event.composedPath() on window behaves the same way as that
on document.

BUG=645527
==========

to

==========
Make event.composedPath() on window behave the same way as that on document

The spec is: https://dom.spec.whatwg.org/#dom-event-composedpath
The relevant change of the spec: https://github.com/whatwg/dom/pull/327

I have updated the DOM Standard to clarify the behavior of event.composedPath()
on
window.

The current Blink's implementation of event.composedPath() on window returns
just [window]. Now, event.composedPath() on window behaves the same way as that
on document.

BUG=645527

Committed: https://crrev.com/92dd0aa2f5587f380f7f8f7c58d1f9a9862e3254
Cr-Commit-Position: refs/heads/master@{#422368}
==========

[commit-bot: I haz the power, 2016-10-03 04:06:24]

Patchset 2 (id:??) landed as
https://crrev.com/92dd0aa2f5587f380f7f8f7c58d1f9a9862e3254
Cr-Commit-Position: refs/heads/master@{#422368}