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

Issue 706522 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature



Sign in to add a comment

Mechanism to expose information to clients outside Chrome.

Project Member Reported by r...@chromium.org, Mar 29 2017

Issue description

There are an increasing number of times when Chrome needs to expose information to clients which are run independently of Chrome. Sometimes, these clients may run even before Chrome has started.

In the past, we've used arbitrary .dotfiles on the stateful partition to expose this information.

We should standardize on the mechanism we want to use to expose this information - with a design clarifying the reasons for picking the mechanism over any other alternatives.

 

Comment 1 by r...@chromium.org, Mar 29 2017

Blocking: 706523

Comment 2 by r...@chromium.org, Apr 13 2017

A short design doc for this feature is here:
http://go/chrome-properties-cros

Comment 3 by r...@chromium.org, Apr 24 2017

Cc: mnissler@chromium.org
Status: WontFix (was: Started)
This is superseded by work being done by mnissler@ - see comments on the design doc.

Comment 4 by r...@chromium.org, Apr 30 2017

Blocking: -706523

Sign in to add a comment