New issue
Advanced search Search tips

Issue 701458 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

[Component Request] Blink>AmbientLight

Project Member Reported by scheib@chromium.org, Mar 14 2017

Issue description

1] Component Name: Blink>AmbientLight

Guideline 1 (Clarity): Component name should be descriptive

Using the name from the W3C spec.
https://w3c.github.io/ambient-light/


Guideline 2 (Permanence): Component names should describe features

Using the name from the W3C spec.
https://w3c.github.io/ambient-light/


Guideline 3 (Specific): Components are meant to explicitly track functional
work areas.

Yes.

Guideline 4 (Discoverable/ Predictable): Components should be parented
where people would logically expect to find them 

Web APIs go in Blink


2] Parent Component: Blink

3] Description of Component: ______

Issues related to the Ambient Light Sensor API https://w3c.github.io/ambient-light/

4] Admin/ Owner: ______

If groups work, please:
device-dev@chromium.org

If not, then:
reillyg@chromium.org,
dougt@chromium.org,
scheib@chromium.org,
mcasas@chromium.org,

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently).

Device API team triages, all of blink is moving to 1 week SLA.
 

Comment 1 by scheib@chromium.org, Mar 14 2017

When we do create this -- https://bugs.chromium.org/p/chromium/issues/detail?id=697068 should be moved to this component.
Owner: lafo...@chromium.org
Status: Fixed (was: Untriaged)
Created component (1).

(1) - https://bugs.chromium.org/p/chromium/components/detail?component=Blink%3EAmbientLight

Sign in to add a comment