Comment 27 for bug 1391230

Building up salveti's comment, the right way to do this is to make use of the application active status in webbrowser-app and use that to stop the media playback, or release the screen on request.

The way I understand the issue right now is that there is no obvious comms path for webbrowser to ask oxide to release the display request? Basically the only process that is told that its being put to the background is the actual application (webbrowser-app), whatever its helper processes do on this information is up to the app; in this case it needs to implement this signal to oxide so that it releases the resource.

NB: Qt.application.active for app state, or its C++ implementation taking the event form the QApplication event loop.