Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX: Don't switch to the source (application, window, tab) you decide to record #403

Open
oas777 opened this issue Feb 6, 2020 · 8 comments
Labels
priority:low Low priority type:documentation Improvements or additions to documentation

Comments

@oas777
Copy link

oas777 commented Feb 6, 2020

I think it's highly irritating that you switch to the source you select when choosing the desktop recording content. Stick in the original browser/tab and show the preview instead.

@LukasKalbertodt
Copy link
Member

This is unfortunately not something we have control over. The browser brings the application/window/tab in the front/makes it active. I did not find a way for the web application to ask the browser not to do that. It might also be a security measure to make it more clear to the user that that window is now captured.

So I'm afraid we probably have to close this as "can't fix this". (And -- not that it matters, but -- I agree with you in that the current behavior is kind of annoying.)

@oas777
Copy link
Author

oas777 commented Feb 7, 2020

Stimmt, das ist mir in anderen Anwendungen so noch nicht aufgefallen. Schade. Wir müssen meines Erachtens die Nutzenden darauf hinweisen. Was wäre die letzte Stelle zwischen "What video source(s) to record?" und dem Wechsel in das dann gewählte Fenster/Tab/Programm, wo du eingreifen kannst? Da, wo "Display" steht oder auch im nachfolgenden Dialogfenster?

@LukasKalbertodt
Copy link
Member

I asked on StackOverflow about this again, but as expected, it doesn't seem like there is anything we can do.

Regarding telling the user: I'm not sure if that's really worth it or if we can properly do that. We basically would have to show this information once the users clicks on the "Display" or "Display&Camera" button. But how to show it? I don't really think there is a good way.

I think in the long term we want a "help" page with an FAQ with all this information. There are a few tricky things when recording a window/your screen anyway. We can address those on that help page. Until then, I'll denote this to low priority for now.

@LukasKalbertodt LukasKalbertodt added type:documentation Improvements or additions to documentation priority:low Low priority labels Feb 13, 2020
@oas777
Copy link
Author

oas777 commented Feb 18, 2020

I agree we need FAQ (or an explaining screencast...) in the long run. My question is whether we have to "warn" the user when selecting the content. Pleas find two suggestions attached, below is the respective text.
tip-2
tip-1

When selecting the display content, STUDIO will put forward that content for you to check; come back to STUDIO to continue the recording process.

Upon selection, STUDIO will put forward that content for you to check; come back to STUDIO to continue the recording process.

@LukasKalbertodt
Copy link
Member

I opened an issue on the getDisplayMedia standard repository. Hopefully people agree that this current behavior is not universally useful. However, even if people agree, it would take quite some time to make it into browsers.

In the meantime... mh. I saw your suggestions. Your first image is not possible as we don't have any control over the popup window. The second one would be possible, but I also don't think it's too great from a design/UX standpoint. Maybe #483 can help here...

@oas777
Copy link
Author

oas777 commented Apr 28, 2020

Thanks, Lukas. Let's hope we can change that in the browsers used in the long run. As for a short-term solution, I see your concerns regarding design/UX/UI, though I doubt the explanation video alone will help. Would it be possible to to provide the information I proposed in the hover-over?

@LukasKalbertodt
Copy link
Member

Something is actually happening in this regard. There now exists CaptureController which can be used to (at least somewhat) control the focus behavior. It is still an experimental feature apparently, but already has full support in Chrome (and Edge).
So it seems we can improve the Studio situation at least for some browsers.

@oas777
Copy link
Author

oas777 commented May 22, 2023

+1. I checked with other services (https://www.screencapture.com/, https://screenapp.io/#/), they have the same "issue". Maybe also worth looking at for their UI/UX. For example, I like the option to get other formats of a given recording

image

which in our case would tell people to run this through Opencast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:low Low priority type:documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants