[screen-wake-lock] Add Mozilla feedback, link to general review feedback (#336)
[screen-wake-lock] Add security considerations section (#338)
[screen-wake-lock] Control screen brightness 🔆 review feedback (#335)
- Anssi Kostiainen via GitHub (Monday, 30 May)
- François Beaufort via GitHub (Monday, 30 May)
- Anssi Kostiainen via GitHub (Monday, 30 May)
- François Beaufort via GitHub (Friday, 27 May)
- François Beaufort via GitHub (Friday, 27 May)
- François Beaufort via GitHub (Monday, 23 May)
- Reilly Grant via GitHub (Friday, 20 May)
- Marcos Cáceres via GitHub (Friday, 20 May)
- Anssi Kostiainen via GitHub (Thursday, 19 May)
- Reilly Grant via GitHub (Friday, 13 May)
- François Beaufort via GitHub (Thursday, 12 May)
- Anssi Kostiainen via GitHub (Tuesday, 10 May)
- Will Morgan via GitHub (Monday, 9 May)
- Anssi Kostiainen via GitHub (Tuesday, 3 May)
- François Beaufort via GitHub (Monday, 2 May)
[screen-wake-lock] Propose high level control flow for JS-style brightness APIs (#339)
[sensors] Current browsing context doesn't exist in workers (#435)
[sensors] Currently focused area needs a top-level browsing context (#436)
[sensors] Reword the "Conditions to expose sensor readings" section (#434)
[vibration] api.Navigator.vibrate - Throwing intervention error of vibration after user already interacted with UI. (#25)
[vibration] Require sticky activation to perform vibrate (#30)
[vibration] Require user activation for navigator.vibrate (#29)
Closed: [screen-wake-lock] Propose high level control flow for JS-style brightness APIs (#339)
Closed: [vibration] api.Navigator.vibrate - Throwing intervention error of vibration after user already interacted with UI. (#25)
Last message date: Tuesday, 31 May 2022 12:22:09 UTC