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

Issue 650866 link

Starred by 1 user
Status: Duplicate
Owner:
tbarzic@chromium.org
Closed: Oct 2016
Cc:
xiy...@chromium.org
abodenha@chromium.org
rdevlin....@chromium.org
r...@chromium.org
michae...@chromium.org
steve...@chromium.org
█ zelidrag@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature

Blocking:
issue 629931



Sign in to add a comment

Enable chrome.networkingPrivate in kiosk sessions

Project Member Reported by tbarzic@chromium.org, Sep 27 2016 
Look into opening chrome.networkingPrivate API to apps running in kiosk mode (task related to issue 629931 for chrome.networkingPrivate).

This would entail renaming the API to chrome.networking.
Before enabling the API in kiosk, it should be reviewed, and amended to be better suited for moving to a public (even if it's only public in kiosk sessions).
We should also figure out which parts of the API (if any) should remain private (and available to white-listed set of apps).

Comment 1 by steve...@chromium.org, Sep 28 2016 

FWIW, I don't have any particular concerns about opening up the networkingPrivate API to kiosk apps (as long as we are careful about how we go about that).

I do have concerns about renaming it or duplicating it, I think that keeping the name "private" helps enforce the "not for general public use" nature of the API.

In order to be useful to kiosk apps, we would probably want to allow them to configure networks, which is the primary reason the API is private, so I don't think we need to be concerned with partially exposing the API.

Comment 2 by tbarzic@chromium.org, Oct 3 2016

Mergedinto: 651488
Status: Duplicate (was: Assigned)

Comment 3 by st...@chromium.org, Mar 3 2017

Cc: r...@chromium.org

Comment 4 by st...@chromium.org, Mar 3 2017

Cc: -st...@chromium.org
►

Sign in to add a comment