also add window.webxdc.isRealtimeSupported() so apps that don't require the feature to work can avoid the dialog pop up and just keep working without real-time, to mitigate annoyances when apps work without realtime and use it only to add extra features opportunistically
window.webxdc.isRealtimeSupported() makes sense in general as some webxdc implementations besides allowing to disable it, might just not support realtime channels feature, as it is more work to implement than the simple basic API, giving the client a way to communicate that the feature is missing without silently doing nothing, so apps can realize the lack of support and adapt or show a warning if they can't work without realtime
I guess this requires the Webxdc spec to be updated as well in some our repos
also add
window.webxdc.isRealtimeSupported()
so apps that don't require the feature to work can avoid the dialog pop up and just keep working without real-time, to mitigate annoyances when apps work without realtime and use it only to add extra features opportunisticallywindow.webxdc.isRealtimeSupported()
makes sense in general as some webxdc implementations besides allowing to disable it, might just not support realtime channels feature, as it is more work to implement than the simple basic API, giving the client a way to communicate that the feature is missing without silently doing nothing, so apps can realize the lack of support and adapt or show a warning if they can't work without realtimeI guess this requires the Webxdc spec to be updated as well in some our repos