LGTM1 Interoperability risk is relatively low. The main risk is that other browsers do not implement the feature. However, since the feature is a small addition to an existing spec and it has consensus across browsers, it is possible that it will be implemented. There is no compatibility risk as the feature is strictly additive and orthogonal to existing features.
I assume that this can be feature detected (as presence or absence of the information) and in non-supporting browsers, the app would fall back to whatever the current behavior is. Is that a reasonable approach for developers? *Gecko*: Positive (https://github.com/w3c/mediacapture-screen-share/pull/315) Since this is a minor addition to an existing spec, no official position was requested as it would have been closed without response. The provided link points to the PR where Firefox's representative was supportive. *WebKit*: Positive (https://github.com/w3c/mediacapture-screen-share/ pull/315) Since this is a minor addition to an existing spec, no official position was requested as it would have been closed without response. The provided link points to the PR where Safari's representative approved. I would typically err on the side of filing a position request regardless of the size of the feature. I don't believe it's common that these would be closed without a response. However, in this specific case I agree that the approval and comments on the pull request seem to be sufficient evidence of support. Thanks, Vlad -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d9537c0d-0f7b-4fd3-9222-fdfd3694ddb8n%40chromium.org.
