You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a guest joins a collaboration session, the file that the host is currently editing is automatically opened within the guest's instance of VS/VS Code. This makes it easy for the guest to immediately orient themselves with the host as they kick off their conversation. However, the guest isn't initially "pinned" to the host, so if the host moved to another file and/or moved their cursor within the active file, the guest wouldn't automatically follow along with them, unless they explicitly pinned to the host after joining (which they may not be aware they can do).
In order to simplify the getting started experience for guests, and potentially model common interactions more naturally (e.g. the host needs to walk the guest through an issue which spans multiple files), we could change the current behavior and pin guests to the host when they first join a session. Since pinning is already disabled once the guest opens a file on their own, or places their cursor within a file, this change wouldn't actually disrupt the user if they didn't need to be pinned. It would simply keep the guest in sync with the host until the moment that they don't need to be, which may be the expected/smoothest experience for bootstrapping collaboration sessions.
Additionally, we could explore adding a new user setting that controls this behavior if necessary, similar to some of our existing "smart defaults" that can be disabled (e.g. auto-joining a shared debugging session).
The text was updated successfully, but these errors were encountered:
@lostintangent It would be great if we can get a status of active or inactive about the guest, when he/she leaves or becomes inactive (moving to another application not exiting live share). Thanks!!
Currently, when a guest joins a collaboration session, the file that the host is currently editing is automatically opened within the guest's instance of VS/VS Code. This makes it easy for the guest to immediately orient themselves with the host as they kick off their conversation. However, the guest isn't initially "pinned" to the host, so if the host moved to another file and/or moved their cursor within the active file, the guest wouldn't automatically follow along with them, unless they explicitly pinned to the host after joining (which they may not be aware they can do).
In order to simplify the getting started experience for guests, and potentially model common interactions more naturally (e.g. the host needs to walk the guest through an issue which spans multiple files), we could change the current behavior and pin guests to the host when they first join a session. Since pinning is already disabled once the guest opens a file on their own, or places their cursor within a file, this change wouldn't actually disrupt the user if they didn't need to be pinned. It would simply keep the guest in sync with the host until the moment that they don't need to be, which may be the expected/smoothest experience for bootstrapping collaboration sessions.
Additionally, we could explore adding a new user setting that controls this behavior if necessary, similar to some of our existing "smart defaults" that can be disabled (e.g. auto-joining a shared debugging session).
The text was updated successfully, but these errors were encountered: