GitLab

The previous approach used a behavior, meaning that any Polymer element
which needs to access the JS Mojo API needs to create its own
InterfacePtr to the Mojo service. In a follow-up CL, I will be adding a
new client of this interface, so it would have been wasteful to create
two separate connections to the service.

This CL converts this behavior to a class-based approach which utilizes
a singleton class which stores a single instance of the pointer.

Bug: 884058
Change-Id: I0b2c13677309b9949a0f26d2f11dd40ea8f15b1c
Reviewed-on: https://chromium-review.googlesource.com/1247035Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594518}