New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 686709 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 676707
issue 686707



Sign in to add a comment

Move parts of Blink public API that Device Sensors impl uses to be Device Sensors client library

Project Member Reported by blundell@chromium.org, Jan 30 2017

Issue description

Currently, several Device Sensors client files are part of the WebKit public API (as they are also used by the Blink device sensors client-side code). As part of servicificying Device Sensors and enabling it to be used by clients other than Blink, this dependency from the Device Sensors impl to the WebKit public API should be removed.

As illustrated in https://codereview.chromium.org/2415083002/, porting these files to live in a Device Service client library is not possible because WebKit's modules/ dir can't depend on such a client library. Thus, they should instead be ported to Mojom (they are defining data structures shared between the impl and the client).
 
Blocking: 686707
Owner: blundell@chromium.org
Status: Started (was: Available)
Summary: Move parts of Blink public API that Device Sensors impl uses to be Device Sensors client library (was: Port parts of Blink public API that Device Sensors impl uses to be in mojom instead)
As discussed in https://groups.google.com/a/chromium.org/forum/#!topic/platform-architecture-dev/w3Led4Govow, we actually are going to take the approach of allowing Blink to use these client files from the Device Service. That email thread explains the reasoning.
Status: Fixed (was: Started)
Fixed by https://codereview.chromium.org/2415083002/.

Comment 4 by ortuno@chromium.org, Apr 21 2017

http://crrev.com/2646093002 introduced a dependency from device_unittest to blink. blundell mentioned that we should add a TODO to remove the dependency once this issue is fixed. Now that this is fixed can we remove the dependency?

Comment 5 by ke...@intel.com, Apr 21 2017

Yes, I'll send a CL to remove that dependency. Thanks.
Components: Internals>Services>Device

Sign in to add a comment