michaelwasserman
commented
4 years ago Currently, we imagine that "Screen 1", "Screen 2 " would suffice, but since the name property would be a string, that allows user agents to provide more "real" names as desired, potentially gated by a permission.
This topic pertains more to the Screen Enumeration proposal; there's a related issue there, which notes that there may not always be a reliable mechanism for obtaining a meaningful display name: https://github.com/spark008/screen-enumeration/issues/13
Since there are potential privacy concerns around exposing screen names, what are the alternatives? Ideally, users would be able to see the real names of their displays when viewing a list of them.
Would names like "Display 1", "Display 2" suffice, or would this create a poor user experience/confusion? Or maybe a permission is ideal from a user/privacy standpoint.