- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Mar 2021 14:31:21 +0000
- To: public-webrtc-logs@w3.org
> The proposal I've made allows the captured-page to set a human readable value. I was not there when label was initially designed but, for capture tracks, the localized device name is used. This makes it potentially easy for a web page to display the source of the track. I think it was the initial intent. On the other hand, this does not make it easy for the web page to reason about the source of the track given the same capture device might end up having different names according the system language. If an application wants to detect AirPods, it seems easier to get 'AirPod' instead of 'Elad's Air Pods' or 'Air Pod de youenn' It is true that there is precedent for non localized track labels with RTCPeerConnection tracks but I doubt labels are used here. And screen share is closer to capture tracks. > But Chrome Security was hesitant about following suit and exposing either the [title](https://developer.mozilla.org/en-US/docs/Web/API/Document/title) or the [URL.host](https://developer.mozilla.org/en-US/docs/Web/API/URL/host) Can you share more about the potential issues here? Or should it be done privately? > which has thus far only been of marginal utility. What is the benefit of using polymorphism here? I see more value personally in deprecating label than extending its use. A dedicated field seems cleaner and there would be no backward compatibility issues as well. > Perhaps you could present a hypothetical example to the contrary? If the capturing web application knows that the label is the window title, the capturing web application will know for sure that it matches the title in the OS window bar presented to the user. That makes it a reliable piece of information to help user know which window is actually being shared. If the captured web page provides its own preferred label, the capturing page does not know what the rationale for the label value is. There is no reason to trust that this piece of information is meaningful to the user. Maybe it was defined by the captured page to help other capturing pages it has tight coupling with. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/159#issuecomment-810310533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 March 2021 14:31:57 UTC