Thursday, 29 February 2024
- Re: [deviceorientation] DeviceMotionEvent atttributes can't be null per current IDL (#91)
- Re: [deviceorientation] DeviceMotionEvent atttributes can't be null per current IDL (#91)
Wednesday, 28 February 2024
- Re: [deviceorientation] DeviceMotionEvent atttributes can't be null per current IDL (#91)
- [deviceorientation] Pull Request: Make DeviceMotionEventInit members nullable with null default
- Re: [deviceorientation] Behavior when event data cannot be provided is underspecified (#118)
Sunday, 25 February 2024
- Re: [deviceorientation] Device motion sampling frequency (#87)
- Re: [deviceorientation] DeviceMotionEvent atttributes can't be null per current IDL (#91)
- Re: [deviceorientation] Guidance needed: how to acquire compass headings in a future-compatible manner? (#137)
- Re: [deviceorientation] Behavior when event data cannot be provided is underspecified (#118)
- Re: [deviceorientation] Malicious use of the phone's Gyroscope (#30)
- Closed: [deviceorientation] Malicious use of the phone's Gyroscope (#30)
- Closed: [deviceorientation] Add way of getting current orientation (#11)
Wednesday, 14 February 2024
- Closed: [deviceorientation] DeviceOrientationEvent.absolute's value when data cannot be obtained (#119)
- Re: [deviceorientation] Security/privacy consideration: cross-origin linkage (#33)
- Closed: [deviceorientation] Security/privacy consideration: cross-origin linkage (#33)
Tuesday, 13 February 2024
- [deviceorientation] Pull Request: Check visibility state in algorithms that fire events
- Re: [deviceorientation] DeviceOrientationEvent: Define absolute's value on error (#139)
- Re: [deviceorientation] DeviceOrientationEvent: Define absolute's value on error (#139)
- [deviceorientation] Pull Request: DeviceOrientationEvent: Define absolute's value on error
Monday, 12 February 2024
- Re: [deviceorientation] DeviceMotionEvent atttributes can't be null per current IDL (#91)
- Re: [deviceorientation] Need to define the DeviceMotionEvent constructor (#83)
- Closed: [deviceorientation] Need to define the DeviceMotionEvent constructor (#83)
- Re: [deviceorientation] Need to define the DeviceMotionEvent constructor (#83)
- Re: [deviceorientation] Add way of getting current orientation (#11)
- Re: [deviceorientation] Security/privacy consideration: cross-origin linkage (#33)
- Re: [deviceorientation] requestPermission() and event handling clarification (#74)
- Closed: [deviceorientation] requestPermission() and event handling clarification (#74)
- Re: [deviceorientation] Accessibility Checklist (#131)
Thursday, 8 February 2024
- Re: [deviceorientation] Internationalization Checklist (#132)
- Closed: [deviceorientation] Internationalization Checklist (#132)
Wednesday, 7 February 2024
Tuesday, 6 February 2024
- Re: [deviceorientation] Wide review tracker (#130)
- Re: [deviceorientation] Wide review tracker (#130)
- Re: [deviceorientation] Wide review tracker (#130)
Monday, 5 February 2024
- Re: [deviceorientation] Wide review tracker (#130)
- Re: [deviceorientation] Same origin S&P requirement conflicts with Permissions Policy integration (#133)
- Re: [deviceorientation] Wide review tracker (#130)
- [geolocation-api] Pull Request: Add `[SecureContext]` tags to the interfaces
Friday, 2 February 2024
- Re: [deviceorientation] Wide review tracker (#130)
- Re: [deviceorientation] Replace same-origin Security & Privacy requirement with Permissions Policy one (#136)
- [deviceorientation] Pull Request: changes: Mention #136 in the Permissions Policy integration item
- Re: [deviceorientation] Replace same-origin Security & Privacy requirement with Permissions Policy one (#136)
- Re: [deviceorientation] Wide review tracker (#130)