-
Notifications
You must be signed in to change notification settings - Fork 4
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
base: main
Are you sure you want to change the base?
Conversation
@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. |
Thanks for working on this @alcooper91 . 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? |
Hey Rik, 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.
Is this referring to e.g. |
Thank you! |
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). |
/agenda to bring to attention of the group |
No description provided.