Re: [sensors] Introduce the Reading Timestamp concept
Re: [sensors] Sensor.timeStamp could be clarified
[sensors] Future proofing terminology
- Re: [sensors] Future proofing terminology
- Re: [sensors] Future proofing terminology
- Re: [sensors] Future proofing terminology
Closed: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency?
Re: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency?
Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors
Re: [sensors] Clarify sensor frequency concepts
Re: [sensors] Editorial fixes to Extensibility section
Closed: [sensors] Addressing finger printing concerns for sensor APIs
Closed: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration
Closed: [sensors] Take into account user gestures as an input for security policy enforcement
Re: [sensors] Take into account user gestures as an input for security policy enforcement
Re: [sensors] Add 'user triggered activation' as mitigation strategy
Re: [sensors] Make 'Conditions to expose sensor readings' must
- Re: [sensors] Make 'Conditions to expose sensor readings' must
- Re: [sensors] Make 'Conditions to expose sensor readings' must
- Re: [sensors] Make 'Conditions to expose sensor readings' must
- Re: [sensors] Make 'Conditions to expose sensor readings' must
- Re: [sensors] Make 'Conditions to expose sensor readings' must
- Re: [sensors] Make 'Conditions to expose sensor readings' must
- Re: [sensors] Make 'Conditions to expose sensor readings' must
Closed: [sensors] Should a "suspended" state be added
Re: [sensors] Should a "suspended" state be added
[sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Re: [sensors] What's the rationale of moving security checks outside of normative requirements?
- Closed: [sensors] What's the rationale of moving security checks outside of normative requirements?
Closed: [sensors] Define algorithm for suspending / resuming activated sensor objects
Closed: [sensors] Should a "suspended" state be added
Closed: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec.
Closed: [sensors] bikeshed link errors
Re: [sensors] bikeshed link errors
Re: [magnetometer] Use value getter operation and use double as attribute type
Re: [ambient-light] Use value getter operation and fix illuminance attribute type
Re: [sensors] Sensor discovery
Re: [sensors] Split security & privacy questionnaire
Re: [proximity] Align with Generic Sensor API current state
Re: [magnetometer] Add security and privacy questionnaire for Magnetometer
- Re: [magnetometer] Add security and privacy questionnaire for Magnetometer
- Re: [magnetometer] Add security and privacy questionnaire for Magnetometer
[sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments from https://github.com/w3c/sensors/pull/270#issuecomment-330579933
- Closed: [sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments
- Re: [sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments
Re: [sensors] Introduce Default Sensor concept
- Re: [sensors] Introduce Default Sensor concept
- Re: [sensors] Introduce Default Sensor concept
- Re: [sensors] Introduce Default Sensor concept
Re: [gyroscope] Define Gyroscope sensor type, clarify latest reading
Re: [sensors] Introduce a Reading Change Treshold concept
Closed: [sensors] Find a clearer name for the sensor concept
Re: [sensors] Fix #193: Define extension spec Security & Privacy expectations
Closed: [sensors] Security issues when used in combination with other APIs
Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269
- Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269
- Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269
- Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269
- Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269
- Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269
- Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269
Closed: [sensors] granularity of Permission name for concrete/ fusion sensors
Closed: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
Re: [sensors] Add information to "Extending the Permission API" section
Re: [sensors] Redefine [=sensor=] concept
Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
- Re: [battery] Allow use in same-origin children
Re: [sensors] Fix Bikeshed custom header rendering bug
Re: [sensors] Answer Security and Privacy self review questionnaire
- Re: [sensors] Answer Security and Privacy self review questionnaire
- Re: [sensors] Answer Security and Privacy self review questionnaire
- Re: [sensors] Answer Security and Privacy self review questionnaire
- Re: [sensors] Answer Security and Privacy self review questionnaire
[sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Re: [sensors] Undefined values makes GS a pain to work with using TypeScript
- Closed: [sensors] Undefined values makes GS a pain to work with using TypeScript
Re: [sensors] Update geolocation.js polyfill
Re: [sensors] Tie [=latest reading=] map to an origin
- Re: [sensors] Tie [=latest reading=] map to an origin
- Re: [sensors] Tie [=latest reading=] map to an origin
- Re: [sensors] Tie [=latest reading=] map to an origin
- Re: [sensors] Tie [=latest reading=] map to an origin
- Re: [sensors] Tie [=latest reading=] map to an origin
[accelerometer] Why unrestricted double for acceleration readings?
- Re: [accelerometer] Why unrestricted double for acceleration readings?
- Re: [accelerometer] Why unrestricted double for acceleration readings?
- Re: [accelerometer] Why unrestricted double for acceleration readings?
[sensors] Review Security and Privacy questionnaire
- Re: [sensors] Review Security and Privacy questionnaire
- Re: [sensors] Review Security and Privacy questionnaire
- Closed: [sensors] Review Security and Privacy questionnaire
Closed: [sensors] Investigate using PWA installed status as indication of user intent
Re: [sensors] Relation to Permissions API
Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Investigate using PWA installed status as indication of user intent
Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
Re: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration
Re: [sensors] Addressing finger printing concerns for sensor APIs
- Re: [sensors] Addressing finger printing concerns for sensor APIs
- Re: [sensors] Addressing finger printing concerns for sensor APIs
Re: [sensors] Annotate interface with [Exposed] extended attribute
Re: [sensors] Use [Exposed=Window]
- Re: [sensors] Use [Exposed=Window]
- Re: [sensors] Use [Exposed=Window]
- Re: [sensors] Use [Exposed=Window]