Intent to Experiment: Element Capture
TAG review
We are holding off on the request for a TAG review until we get some more developer feedback about the API shape.
TAG review status
Pending
Risks
Interoperability and Compatibility
Gecko: Under consideration (https://twitter.com/quicksave2k/status/1583388663597015042
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Goals for experimentation
* Solicit more informed Web developer feedback to validate the API shape.
* Ensure that the feature works correctly in conjunction with adjacent features.
Debuggability
No changes to DevTools are intended.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
No
This API is supported on all desktop platforms. Mobile platforms are unsupported because screen-capture itself is unsupported on those platforms.
Is this feature fully tested by https://chromestatus.com/feature/5198989277790208
Links to previous Intent discussions
Intent to prototype: This intent message was generated by Chrome Platform Status.
Mike Taylor
Hi Elad,
Can you clarify which milestones you intend to experiment in?
thanks,
Mike
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visitMike Taylor
Nov 21, 2023, 5:39:28 AM11/21/23Reply to authorSign in to reply to authorForwardSign in to forwardDeleteYou do not have permission to delete messages in this groupCopy linkReport messageShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto Elad Alon, blink-devThanks, LGTM to experiment from 121 to 126 inclusive.
Elad Alon
May 10, 2024, 10:44:53 PM5/10/24Reply to authorSign in to reply to authorForwardSign in to forwardDeleteYou do not have permission to delete messages in this groupCopy linkReport messageShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto blink-dev, Elad Alon, [email protected]Hello Blink owners,
We are asking for a breaking period of 3 weeks to this API, followed by a renewed experiment for the traditional 6 milestones (2024-May-14 to 2024-Jun-04). A TAG request has now been submitted.
Signals: Signals have been requested. Mozilla responded. We intend to prioritize this discussion with them now.
Feedback: Outreach for feedback from the spec community - multiple
unread,Mike Taylor
May 11, 2024, 8:25:03 AM5/11/24Reply to authorSign in to reply to authorForwardSign in to forwardDeleteYou do not have permission to delete messages in this groupCopy linkReport messageShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto Elad Alon, blink-dev, [email protected]Note: Because you're asking for a renewal of 6 milestones, this will require 3 LGTMs.
Can you clarify which milestones you're asking for? You've written "(2024-May-14 to 2024-Jun-04)" - that range maps to M125 and M126 stable releases.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].To view this discussion on the web visitMike Taylor
May 15, 2024, 6:36:43 AM5/15/24Reply to authorSign in to reply to authorForwardSign in to forwardDeleteYou do not have permission to delete messages in this groupCopy linkReport messageShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto Elad Alon, blink-dev, [email protected], Panos AstithasOK - thanks for the clarification. I would ask that you get in touch with every registered origin - expiring the experiment early may be surprising.
LGTM1 to experiment from M127 to M132 inclusive.
Chris Harrelson
May 15, 2024, 6:40:42 AM5/15/24Reply to authorSign in to reply to authorForwardSign in to forwardDeleteYou do not have permission to delete messages in this groupCopy linkReport messageShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto Mike Taylor, Elad Alon, blink-dev, [email protected], Panos AstithasLGTM2To view this discussion on the web visitYoav Weiss (@Shopify)
May 16, 2024, 2:41:36 AM5/16/24Reply to authorSign in to reply to authorForwardSign in to forwardDeleteYou do not have permission to delete messages in this groupCopy linkReport messageShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto Chris Harrelson, Mike Taylor, Elad Alon, blink-dev, [email protected], Panos AstithasLGTM3To view this discussion on the web visitFrançois Beaufort
Jul 22, 2024, 6:48:11 PM7/22/24Reply to authorSign in to reply to authorForwardSign in to forwardDeleteYou do not have permission to delete messages in this groupCopy linkReport messageShow original messageEither email addresses are anonymous for this group or you need the view member email addresses permission to view the original messageto Danny Moerkerke, [email protected], blink-dev, Elad Alon, Yoav Weiss, [email protected], [email protected], Panos Astithas, Chris HarrelsonNote that I can also reproduce this issue with https://element-capture-demo.glitch.me/
@[email protected] Can you help us fix this?My understanding was that the breaking period was between June 24 and July 15. The issue happens for both old and new tokens.
