We've just had a call to discuss this, the outcome is the following:
Make use of com.canonical.Unity.WindowStack API (from QtMir) to implement a state tracker in Oxide, so that it is aware when its webbrowser-app process has gone out of focus, in order to release the screen request and let the system suspend. In the same way, Oxide must retake the request once the process comes back into focus, so that playback may continue.
We've just had a call to discuss this, the outcome is the following:
Make use of com.canonical. Unity.WindowSta ck API (from QtMir) to implement a state tracker in Oxide, so that it is aware when its webbrowser-app process has gone out of focus, in order to release the screen request and let the system suspend. In the same way, Oxide must retake the request once the process comes back into focus, so that playback may continue.