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

Port explainer from initial proposal #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alcooper91
Copy link

No description provided.

@alcooper91
Copy link
Author

@cabanier PTAL, this is just porting my initial proposal into a more formal location; I think if we want to spend more time iterating on the shape, etc. we can do that in a future change.

@cabanier
Copy link
Member

Thanks for working on this @alcooper91 .
I'm still unconvinced if this API is needed. For the use cases you list, it would be more convenient to the user to just use the system's screen recording functionality. Do you need this API because screen recording is too hard to reach on handheld devices?

Looking at the 2D version of the screen capture API, it seems more targeted in sharing your screen with others. Is that a better use case for this proposal?

@alcooper91
Copy link
Author

Hey Rik,
My primary motivation for doing this move here was to help address immersive-web/webxr#1200 (and the further discussion in immersive-web/proposals#68) per the discussion at TPAC where I was asked to port this to a more public place.

My initial step here was to just take my old explainer from my personal repo to here as a jumping off point for us to refine the shape of things; though it's not something that we are actively working on at the moment.

Per my read, there is a desire for Web Developers to trigger this system capture from within their experience (e.g. without forcing you to leave it and initiate the system recording) and then be able to do something with it. An acceptable implementation of this API does then become simply triggering that system recording/prompt/ui and optionally providing a mechanism to directly put that recording into the WebShare API.

Looking at the 2D version of the screen capture API, it seems more targeted in sharing your screen with others. Is that a better use case for this proposal?

Is this referring to e.g. getDisplayMedia ? I put a section on why I felt it wasn't a viable path in the explainer; but essentially the intention with the API I'm proposing is to be lower friction and to be extensible for other recording types in the future if we want that.

@AdaRoseCannon
Copy link
Member

Thank you!

@alcooper91
Copy link
Author

It's also worth noting that while the System functionality may be ideal; it seems as though (from discussion on the WebXR issue) developers are simply compositing their own capture (and requesting raw camera access where needed to do so for immersive-ar).

@AdaRoseCannon
Copy link
Member

/agenda to bring to attention of the group

@probot-label probot-label bot added the agenda label Oct 2, 2023
@Yonet Yonet removed the agenda label Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants