-
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
Vote: Adopt spec by Screen Capture Community Group #9
Comments
I support adopting the Capture all screens specification. |
1 similar comment
I support adopting the Capture all screens specification. |
I support adopting the Capture All Screens specification; we at Dialpad intend to use it soon for Agent Screen Capture . |
I support adopting the Capture All Screens specification; we at Edify intend to use it soon for agent screen capture. |
I support adopting the Capture All Screens specification; we at NICE intend to use it soon for Agent Screen Capture. |
I support adopting the Capture All Screens specification; we at Observe intend to use it soon for Agent screen capture. |
This issue collects votes for the Screen Capture Community Group to adopt the Capture All Screens spec.
The recommended format for casting your vote is to use one of the following:
Mentioning which company you work with, and whether you have a specific use-case in mind for this API, helps browser vendors set the prioritization of implementing this API. For some browser vendors, such "Web developer signals" are taken into account when deciding whether an API is ready to be shipped.
The text was updated successfully, but these errors were encountered: