oxide team mailing list archive

[David Barth <david.barth@xxxxxxxxxxxxx>]

*1. Release*

   - 1.9.5 - released for OTA-7 with the memory limit fixes and upstream
   security fixes
   - 1.10 - around the corner; initial releases planned next week


*2. Feature*

   - WebRTC/Hangout support on Desktop - technical enablement ready at the
   Oxide level (WebRTC + camera support) + there is a webbrowser-app branch
   being worked on (Olivier)
   - Chris started working on site settings
   - Trust prompt for site location or camera access: we can't merge the
   trust prompt and request dialogs
   - accelerometer & vibrate API branches to be refreshed; to be reviewed
   next week (Alex, Chris)


*3. Bugs*

   - Recent regression fixed in 1.9.5 with the viewport meta


*4. Misc.*

We discussed how to support playing webradio streams only with Oxide, and
how push notifications helpers could wake-up and communicate with a webapp
to transmit their payload.
Oxide should be able  to support the 2 cases already, provided it is given:
1. the right permissions from an apparmor perspective (transitions between
the push components notably)
2. it is authorized to keep running, or interact with components of the
app. lifecycle manager to do so; note: all of the Oxide process tree would
need to run at the point where it is meant to do processing, not just parts
of it though
3. the MH arbitration API needs to be in place to do the right thing when
playing in the background

Single Process mode was also discussed. This remains as a potential mode
for optimizing the webapp cases, but more benchmarking would be needed.
This seems like a low priority considering the recent improvements (memory
limit fixes, crash handler).