Provide web contents to Chrome's mojo services

Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service.
This allows the service implementation to access WebContents-specific
data and show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
Committed: https://crrev.com/6ebc6f22f9eb3c0ebda41830f1aae1e225141a8e
Cr-Commit-Position: refs/heads/master@{#388310}

[please use gerrit instead, 2016-04-19 18:37:05]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo services implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested a service. This
allows the service implementation to access WebContents-specific data as
well as show UI on top of the WebContents.

In addition, this patch renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implement the mojo PaymentRequest
service and the UI specifics are implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested a service. This
allows the service implementation to access WebContents-specific data as
well as show UI on top of the WebContents.

In addition, this patch renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implement the mojo PaymentRequest
service and the UI specifics are implemented in a separate class.

BUG=587995
==========

[please use gerrit instead, 2016-04-19 18:37:28]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested a service. This
allows the service implementation to access WebContents-specific data as
well as show UI on top of the WebContents.

In addition, this patch renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implement the mojo PaymentRequest
service and the UI specifics are implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data as
well as show UI on top of the WebContents.

In addition, this patch renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implement the mojo PaymentRequest
service and the UI specifics are implemented in a separate class.

BUG=587995
==========

[please use gerrit instead, 2016-04-19 18:38:09]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data as
well as show UI on top of the WebContents.

In addition, this patch renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implement the mojo PaymentRequest
service and the UI specifics are implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service and the UI specifics are implemented in a separate class.

BUG=587995
==========

[please use gerrit instead, 2016-04-19 18:38:25]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service and the UI specifics are implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service and the UI functionality is implemented in a separate class.

BUG=587995
==========

[please use gerrit instead, 2016-04-19 18:38:45]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service and the UI functionality is implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

[please use gerrit instead, 2016-04-19 18:39:42]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
that correspond to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

[please use gerrit instead, 2016-04-19 18:40:45]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service. This
allows the service implementation to access WebContents-specific data and
show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service.
This allows the service implementation to access WebContents-specific
data and show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

[please use gerrit instead, 2016-04-19 18:41:24]

rouslan@chromium.org changed reviewers:
+ tedchoc@chromium.org

[please use gerrit instead, 2016-04-19 18:41:25]

tedchoc@, ptal.

[Ted C, 2016-04-19 20:18:55]

lgtm

[please use gerrit instead, 2016-04-19 21:07:52]

The CQ bit was checked by rouslan@chromium.org

[commit-bot: I haz the power, 2016-04-19 21:08:27]

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

[commit-bot: I haz the power, 2016-04-19 21:13:46]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service.
This allows the service implementation to access WebContents-specific
data and show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service.
This allows the service implementation to access WebContents-specific
data and show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

[commit-bot: I haz the power, 2016-04-19 21:13:47]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-22 19:16:22]

Description was changed from

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service.
This allows the service implementation to access WebContents-specific
data and show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995
==========

to

==========
Provide web contents to Chrome's mojo services

For the mojo service implementations in Chrome that fulfill tasks for
render frames, the ChromeServiceRegistrar should provide the WebContents
object that corresponds to the render frame that requested the service.
This allows the service implementation to access WebContents-specific
data and show UI on top of the WebContents.

This patch also renames PaymentRequestDialog.java into
PaymentRequestImpl.java, because it implements the mojo PaymentRequest
service, while the UI functionality is implemented in a separate class.

BUG=587995

Committed: https://crrev.com/6ebc6f22f9eb3c0ebda41830f1aae1e225141a8e
Cr-Commit-Position: refs/heads/master@{#388310}
==========

[commit-bot: I haz the power, 2016-04-22 19:16:23]

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