[blink-dev] Re: Intent to Ship: Region Capture

The discussions around Region Capture have been brought up with TAG again (after their original approval of the design). Here are the minutes from that second meeting: https://github.com/w3ctag/meetings/blob/gh-pages/2

Re: [blink-dev] Re: Intent to Ship: Region Capture

Either m104 or m105. (The Origin Trial is approved until m104, inclusive.) On Mon, May 2, 2022 at 7:46 PM Joe Medley wrote: > When do you intend to ship this? 103? > Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | > 816-678-7195 <(816)%20678-7195> > *If an API's not documente

[blink-dev] Re: Intent to Ship: Region Capture

Thank you, Yoav. I'll definitely follow up on those PRs. On Tuesday, May 24, 2022 at 11:46:44 AM UTC+2 yoav...@chromium.org wrote: > After carefully studying the discussions on the various threads (as well > as participating in them, trying to bridge the gaps), my previous LGTM > still stands.

[blink-dev] Intent to Prototype: DisplayMediaStreamConstraints.systemAudio

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1q3oGy7hLJmdQA4ZK7QG7DnwgtcpL6oB2pqLQJ6MP1tY/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/222/files Summary Hint indicating to the user agent whether the application, upon cal

[blink-dev] Intent to Ship: DisplayMediaStreamConstraints.systemAudio

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1q3oGy7hLJmdQA4ZK7QG7DnwgtcpL6oB2pqLQJ6MP1tY/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/222/files Summary Hint indicating to the user agent whether the application, upon cal

[blink-dev] Intent to Prototype: DisplayMediaStreamConstraints.selfBrowserSurface

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1M63lyDHV-v6LPFzHjfsjBDMfyn075pySa3xfIRSB9zU/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/216/files Summary Hint allowing Web applications to instruct the browser whether, upo

[blink-dev] Intent to Ship: DisplayMediaStreamConstraints.selfBrowserSurface

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1M63lyDHV-v6LPFzHjfsjBDMfyn075pySa3xfIRSB9zU/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/216/files Summary Hint allowing Web applications to instruct the browser whether, upo

[blink-dev] Intent to Prototype: MediaTrackSupportedConstraints.suppressLocalAudioPlayback

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1OmuV1W4f2UvToeNxUVGHv8NcFuL63r94gWwz9i_-VBc/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/164/files Summary Consider a Web application APP which is display-capturing a tab TAB

[blink-dev] Intent to Ship: MediaTrackSupportedConstraints.suppressLocalAudioPlayback

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1OmuV1W4f2UvToeNxUVGHv8NcFuL63r94gWwz9i_-VBc/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/164/files Summary Consider a Web application APP which is display-capturing a tab TAB

[blink-dev] Intent to Prototype: MediaTrackConstraintSet.displaySurface

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1uI51R4YfFQtfiDTw1KfnLqzIu45OgxhYoUT7khlhmwQ/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/186/files Summary When getDisplayMedia() is called, the browser offers the user a cho

[blink-dev] Intent to Ship: MediaTrackConstraintSet.displaySurface

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1uI51R4YfFQtfiDTw1KfnLqzIu45OgxhYoUT7khlhmwQ/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/186/files Summary When getDisplayMedia() is called, the browser offers the user a cho

[blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

Okay, will do. (I've also sent a personal email on the day the intent went out.) When shall I ping this thread if no response is received? On Wed, Jun 1, 2022 at 8:30 AM Yoav Weiss wrote: > > > On Wednesday, May 25, 2022 at 2:38:53 PM UTC+2 Elad Alon wrote: > >> Contact emailselada...@chromium.o

[blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

I've set my alarm. I'll implicitly assume the same period is intended for the other three intents-to-ship sent at roughly the same time. On Wed, Jun 1, 2022 at 9:29 AM Yoav Weiss wrote: > Let's give them 1 more week to respond. > > On Wed, Jun 1, 2022 at 9:21 AM Elad Alon wrote: > >> Okay, will

[blink-dev] Re: Intent to Ship: MediaTrackConstraintSet.displaySurface

Thanks. I've set myself a reminder to ping this thread in one week, as suggested on the other intent thread. On Wed, Jun 1, 2022 at 8:42 AM Yoav Weiss wrote: > > > On Wednesday, May 25, 2022 at 2:47:50 PM UTC+2 Elad Alon wrote: > >> Contact emailselada...@chromium.org >> >> Explainer >> https://

[blink-dev] Re: Intent to Ship: MediaTrackSupportedConstraints.suppressLocalAudioPlayback

> > Similar to other intents, this doesn't count as an official positive > signal. Let's wait a few days to see if one emerges. Thanks. I've set a reminder to ping this thread in one week, as suggested in the other intent thread. On Wed, Jun 1, 2022 at 8:42 AM Yoav Weiss wrote: > > > On Wednes

[blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.selfBrowserSurface

> > Similar to other intents, this doesn't count as an official positive > signal. Let's wait a few days to see if one emerges. I've set a reminder to ping this thread in one week, as suggested in the other intent thread. Any external signals from developers? https://goo.gle/developer-signals

[blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

Hi Alex, Yes, I can initiate TAG review. Would it work for you if I initiated one TAG review-request that referenced all four intents? Or alternatively, four TAG requests? My own feeling is that a joint explainer might be a bit confusing, since the four surfaces are not very closely related. I don

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

: > > > On Wed, Jun 1, 2022 at 9:40 AM 'Elad Alon' via blink-dev < > blink-dev@chromium.org> wrote: > >> Hi Alex, >> >> Yes, I can initiate TAG review. Would it work for you if I initiated one >> TAG review-request that referenced all four i

[blink-dev] Re: Intent to Ship: Region Capture

Quick clarification - the I2E specified this tidbit, which was omitted from the I2S. It applies to both: *Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?* No. This feature is supported on all *desktop* platforms, bu

Re: [blink-dev] Intent to Experiment: Conditional Focus

m therefore asking that shifting the experiment's time window will happen without a breaking period. Thanks, Elad On Monday, January 31, 2022 at 12:21:48 PM UTC+1 Daniel Bratell wrote: > LGTM to shift to M99-M102. Hope you can get some good feedback. > > /Daniel > On 2022-01-31

[blink-dev] Re: Intent to Ship: MediaTrackSupportedConstraints.suppressLocalAudioPlayback

Hi Andy, How does the capturing web app (i.e. Meet) know what I want to do with > audio? The capturing application might know that you're in a physical room and "presenting" to the equipment there. - You use a special user-journey to trigger sharing to a room. - The application could be "

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

Hello Blink owners, I am working to align getDisplayMedia() and the Extension API, to the point that deprecating the Hangouts Extension would be possible. It's going to be a gradual process with multiple changes required. Shipping this one particular API surface (systemAudio) in the next Chrome

[blink-dev] Intent to Prototype: DisplayMediaStreamConstraints.surfaceSwitching

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1kqdLoUcwWe8znVCMXyz2FHk9WMylHbIo7gUjhyHmY_w/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/225/files Summary Programmatically control whether Chrome exposes a button that allow

[blink-dev] Intent to Ship: DisplayMediaStreamConstraints.surfaceSwitching

Contact emailselada...@chromium.org Explainer https://docs.google.com/document/d/1kqdLoUcwWe8znVCMXyz2FHk9WMylHbIo7gUjhyHmY_w/edit?usp=sharing Specificationhttps://github.com/w3c/mediacapture-screen-share/pull/225/files Summary Programmatically control whether Chrome exposes a button that allow

[blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.surfaceSwitching

Hello Blink owners. I know that this is a bit early, as TAG has not yet responded, and the official requests for positions have not had enough time for an official response. I will ping this thread when it's time. (I wanted to get some of the technical prerequisites out of the way before going o

[blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.surfaceSwitching

For the record, Firefox has now formally set their position as *non-harmful*. See here . On Thursday, June 16, 2022 at 7:38:27 PM UTC+2 Elad Alon wrote: > Hello Blink owners. I know that this is a bit early, as TAG has

Re: [blink-dev] Re: Intent to Ship: MediaTrackConstraintSet.displaySurface

iss wrote: >> >> LGTM2 >> >> On Wednesday, June 22, 2022 at 5:41:11 PM UTC+2 Chris Harrelson wrote: >> >>> LGTM1 >>> >>> On Wed, Jun 1, 2022 at 12:37 AM 'Elad Alon' via blink-dev < >>> blink-dev@chromium.org> wrote: >

Re: [blink-dev] Re: Intent to Ship: MediaTrackSupportedConstraints.suppressLocalAudioPlayback

When I have an exact date, I will update ChromeStatus and ping this thread with the target. Currently, I only know that it will be before EoY, but no earlier than August. On Wed, Jun 22, 2022 at 7:16 PM Joe Medley wrote: > When do you hope to ship this? > Joe Medley | Technical Writer, Chrome De

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.selfBrowserSurface

te: >> >> LGTM2 >> >> On Wednesday, June 22, 2022 at 5:42:36 PM UTC+2 Chris Harrelson wrote: >> >>> LGTM1 >>> >>> On Wed, Jun 1, 2022 at 8:45 AM 'Elad Alon' via blink-dev < >>> blink-dev@chromium.org> wrote: >>

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.surfaceSwitching

te: >> >> LGTM2 >> >> On Wednesday, June 22, 2022 at 5:45:12 PM UTC+2 Chris Harrelson wrote: >> >>> LGTM1 >>> >>> On Fri, Jun 17, 2022 at 12:12 AM 'Elad Alon' via blink-dev < >>> blink-dev@chromium.org> wrote: >

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

Thanks you all! On Tuesday, June 21, 2022 at 6:45:57 PM UTC+2 Chris Harrelson wrote: > LGTM3 > > On Thu, Jun 16, 2022 at 5:12 AM Mike Taylor wrote: > >> LGTM2 >> >> On 6/16/22 9:42 AM, Yoav Weiss wrote: >> >> LGTM1 to ship this without waiting on TAG feedback. Please add a feature >> flag just

[blink-dev] Intent to Extend Experiment: Conditional Focus

Hi Blink owners, We'd like to extend the Conditional Focus experiment. It is currently running m102-m105, and we'd like to extend by 3 additional milestones, making it m102-m108 (inclusive). Contact emailselada...@chromium.org Explainerhttps://github.com/WICG/conditional-focus/blob/main/README.m

Re: [blink-dev] Re: Intent to Ship: MediaTrackConstraintSet.displaySurface

nted it doesn't exist.* >> >> >> On Wed, Jun 22, 2022 at 9:13 AM Daniel Bratell wrote: >> >>> LGTM3 >>> >>> /Daniel >>> On 2022-06-22 17:41, Yoav Weiss wrote: >>> >>> LGTM2 >>> >>> On Wednesda

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.selfBrowserSurface

it doesn't exist.* >> >> >> On Wed, Jun 22, 2022 at 9:17 AM Daniel Bratell wrote: >> >>> LGTM3 >>> >>> /Daniel >>> On 2022-06-22 17:42, Yoav Weiss wrote: >>> >>> LGTM2 >>> >>> On Wednesday, June 22,

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

This is shipping in m105. On Thursday, June 23, 2022 at 10:28:26 AM UTC+2 Elad Alon wrote: > Thanks you all! > > On Tuesday, June 21, 2022 at 6:45:57 PM UTC+2 Chris Harrelson wrote: > >> LGTM3 >> >> On Thu, Jun 16, 2022 at 5:12 AM Mike Taylor wrote: >> >>> LGTM2 >>> >>> On 6/16/22 9:42 AM, Yoav

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.surfaceSwitching

it doesn't exist.* >> >> >> On Wed, Jun 22, 2022 at 9:17 AM Daniel Bratell wrote: >> >>> LGTM3 >>> >>> /Daniel >>> On 2022-06-22 17:45, Yoav Weiss wrote: >>> >>> LGTM2 >>> >>> On Wednesday

Re: [blink-dev] Intent to Extend Experiment: Conditional Focus

x27;ll have more time to get feedback. On Friday, August 19, 2022 at 7:35:32 AM UTC-7 mike...@chromium.org wrote: > LGTM to extend to M108 inclusive. > > On 8/18/22 4:33 PM, 'Elad Alon' via blink-dev wrote: > > Hi Blink owners, > > We'd like to extend the Conditi

[blink-dev] Intent to Extend Experiment: Conditional Focus

Hi Blink owners, We'd like to extend the Conditional Focus experiment again. It is currently running m102-m108, and we'd like to extend by 3 additional milestones, making it m102-m111 (inclusive). There has been significant progress in discussions lately, and we have a new API shape which has rou

[blink-dev] Re: Intent to Extend Experiment: Conditional Focus

Turns out that sending a second email with the exact same subject line, gets the message routed to the original thread. Interesting. I'll use another subject line now. :-) On Wednesday, September 21, 2022 at 9:50:25 AM UTC+2 Elad Alon wrote: > Hi Blink owners, > > We'd like to extend the Condit

[blink-dev] Intent to Extend Experiment #2: Conditional Focus

Hi Blink owners, We'd like to extend the Conditional Focus experiment again. It is currently running m102-m108, and we'd like to extend by 3 additional milestones, making it m102-m111 (inclusive). There has been significant progress in discussions lately, and we have a new API shape which has rou

[blink-dev] Re: Intent to Extend Experiment: Conditional Focus

The new thread is now here: https://groups.google.com/a/chromium.org/g/blink-dev/c/R90_BzkM_jY On Wednesday, September 21, 2022 at 9:51:23 AM UTC+2 Elad Alon wrote: > Turns out that sending a second email with the exact same subject line, > gets the message routed to the original thread. Intere

[blink-dev] Re: Intent to Extend Experiment #2: Conditional Focus

For posterity - a Blink owner ended up LGTMing this request on the original thread . On Wednesday, September 21, 2022 at 9:52:29 AM UTC+2 Elad Alon wrote: > Hi Blink owners, > > We'd like to extend the Conditional Focus experime

[blink-dev] Intent to Ship: Conditional Focus

Contact emailselada...@chromium.org Explainerhttps://github.com/WICG/conditional-focus/blob/main/README.md Specification https://w3c.github.io/mediacapture-screen-share/#dom-capturecontroller-setfocusbehavior Design docs https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6w

[blink-dev] Re: Intent to Ship: Conditional Focus

Update - Firefox have officially marked this as "positive". On Thursday, October 13, 2022 at 10:24:11 PM UTC+2 Elad Alon wrote: > Contact emailselad...@chromium.org > > Explainerhttps://github.com/WICG/conditio

Re: [blink-dev] Intent to Ship: Conditional Focus

> On Thu, Oct 13, 2022 at 10:24 PM 'Elad Alon' via blink-dev < > blin...@chromium.org> wrote: > >> Contact emailselad...@chromium.org >> >> Explainerhttps://github.com/WICG/conditional-focus/blob/main/README.md >> >> Specification >> http

Re: [blink-dev] Intent to Ship: Conditional Focus

oportionate difficulty of >>>> testing this API reliably using WPT. >>>> >>> >>> Might be worthwhile to file bugs against WPT/TestDriver for issues you >>> ran into, or missing features. >>> >>> >>>> >>>> O

Re: [blink-dev] Intent to Ship: Conditional Focus

Thanks for approving. May this be a gapless ship? This would show consideration to our OT partners and their effort. On Wednesday, October 19, 2022 at 5:58:25 PM UTC+2 Daniel Bratell wrote: > LGTM3 > > /Daniel > > *Sent with my Thunderbird* > > On 2022-10-19 17:55, 

Re: [blink-dev] Re: Intent to Ship: MediaTrackSupportedConstraints.suppressLocalAudioPlayback

This is shipping in m109. On Wednesday, June 22, 2022 at 7:20:42 PM UTC+2 Elad Alon wrote: > When I have an exact date, I will update ChromeStatus and ping this thread > with the target. Currently, I only know that it will be before EoY, but no > earlier than August. > > On Wed, Jun 22, 2022 at

[blink-dev] Intent to Prototype: Conditional Focus

Contact emailselada...@chromium.org Explainer https://github.com/eladalon1983/conditional-focus/blob/main/README.md Specificationhttps://eladalon1983.github.io/conditional-focus/ Summary Extend the getDisplayMedia APIs to ensure that tab-capture and window-capture return a new subclass of Media

[blink-dev] Intent to Experiment: Conditional Focus

Contact emailselada...@chromium.org Explainer https://github.com/eladalon1983/conditional-focus/blob/main/README.md Specificationhttps://eladalon1983.github.io/conditional-focus/ Design docs https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM/ Summary Extend the get

Re: [blink-dev] Intent to Experiment: Conditional Focus

> > Might be good to move this to WICG to facilitate contributions (given > support > ). > WICG issue #37 asked for this to be adopted by the WICG. (The same partner supported it t

Re: [blink-dev] Intent to Experiment: Conditional Focus

m99, inclusive. So four milestones in total. On Thu, Sep 23, 2021 at 3:53 PM Yoav Weiss wrote: > > > On Thu, Sep 23, 2021 at 3:00 PM Elad Alon wrote: > >> Might be good to move this to WICG to facilitate contributions (given >>> support >>>

[blink-dev] Intent to Prototype: Region Capture

Contact emailselada...@chromium.org, mfo...@chromium.org, jop...@chromium.org Explainerhttps://github.com/eladalon1983/region-capture/blob/main/README.md Specificationhttps://eladalon1983.github.io/region-capture/ Summary Recall that applications may currently obtain a capture of the tab in whi

[blink-dev] Intent to Experiment: Region Capture

Contact emailselada...@chromium.org, mfo...@chromium.org, jop...@chromium.org Explainerhttps://github.com/eladalon1983/region-capture/blob/main/README.md Specificationhttps://eladalon1983.github.io/region-capture/ Summary Recall that applications may currently obtain a capture of the tab in whi

Re: [blink-dev] Intent to Experiment: Region Capture

Thanks for catching that typo. The corrected request is m97 - m100. On Thu, Oct 7, 2021 at 9:20 AM Yoav Weiss wrote: > Do I understand correctly and you want to experiment for a single > milestone? (M97) > > On Tue, Oct 5, 2021 at 11:12 PM 'Elad Alon' via blink-dev <

Re: [blink-dev] Intent to Extend Experiment: Capture Handle

> Agreed about strong positive signals from developers. >> >> On Tuesday, August 17, 2021 at 10:56:26 AM UTC+2 yoav...@chromium.org >> wrote: >> >>> On Mon, Aug 16, 2021 at 11:42 PM 'Elad Alon' via blink-dev < >>> blin...@chromium.org> wro

Re: [blink-dev] Intent to Extend Experiment: Capture Handle

t;>> >>> On Tuesday, August 17, 2021 at 10:56:26 AM UTC+2 yoav...@chromium.org >>> wrote: >>> >>>> On Mon, Aug 16, 2021 at 11:42 PM 'Elad Alon' via blink-dev < >>>> blin...@chromium.org> wrote: >>>> >>>&g

Re: [blink-dev] Intent to Experiment: Region Capture

> > When looking at the API, I found that it's unclear why a cropID is needed > (compared to using an element ID instead, or just passing the element to > `cropTo`). Would be good to further explain that. > Will do along with my next pass over the spec and README, which I intend to do after w

Re: [blink-dev] Intent to Extend Experiment: Capture Handle

> >>>> On Tuesday, August 17, 2021 at 3:41:14 PM UTC+2 Elad Alon wrote: >>>> >>>>> Thanks, Yoav. >>>>> Yes, I intend to formally reach out to Mozilla and Apple soon. >>>>> Agreed about strong positive signals from devel

Re: [blink-dev] Intent to Extend Experiment: Capture Handle

quot;during this time"? During the break, >>>>> or after it? >>>>> >>>>> >>>>>> >>>>>>> On Friday, August 20, 2021 at 6:44:10 AM UTC+2 yoav...@chromium.org >>>>>>> wrote: >>>>>

Re: [blink-dev] Intent to Experiment: Conditional Focus

The partner I had for this feature had a change of scheduling, and will only be set to deploy their test use of it in about a month. I would therefore like to reset this experiment, stopping it for 3 weeks and then starting it afresh in m99-m102 (inclusive). Wdys? Relevant: Discussions about sta

Re: [blink-dev] Intent to Experiment: Conditional Focus

My partners for this feature have not yet been able to take advantage of it, due to scheduling constraints on their end, and so could not yet file feedback. I don't see feedback from anyone else. On Wednesday, January 26, 2022 at 6:00:51 PM UTC+1 mk...@chromium.org wrote: > Hey Elad! > > Did an

[blink-dev] Intent to Experiment: Capture handle

Contact emailselada...@chromium.org Explainerhttps://github.com/WICG/capture-handle/blob/main/README.md Specificationhttps://wicg.github.io/capture-handle/ ("Identity" part) Summary We introduce a mechanism that allows an application to opt-in to exposing certain information to other applicatio

[blink-dev] Re: Intent to Experiment: Capture handle

*Intent to extend experiment, I mean. On Friday, March 4, 2022 at 3:34:12 PM UTC+1 Elad Alon wrote: > Contact emailselad...@chromium.org > > Explainerhttps://github.com/WICG/capture-handle/blob/main/README.md > > Specificationhttps://wicg.github.io/capture-handle/ ("Identity" part) > > Summary >

Re: [blink-dev] Re: Intent to Experiment: Capture handle

Thanks! To clarify, is this inclusive? On Fri, Mar 4, 2022 at 4:42 PM Yoav Weiss wrote: > LGTM to continue experimenting till M102 > > On Fri, Mar 4, 2022 at 3:36 PM 'Elad Alon' via blink-dev < > blink-dev@chromium.org> wrote: > >> *Intent to extend experim

[blink-dev] Intent to Ship: Capture handle

Contact emailselada...@chromium.org Explainer https://github.com/w3c/mediacapture-handle/blob/main/identity/README.md Specificationhttps://w3c.github.io/mediacapture-handle/identity/ Summary We introduce a mechanism that allows an application to opt-in to exposing certain information to other a

[blink-dev] Intent to Extend Experiment: Region Capture

Contact emailselada...@chromium.org, mfo...@chromium.org, jop...@chromium.org Explainerhttps://github.com/w3c/mediacapture-region/blob/main/README.md Specificationhttps://w3c.github.io/mediacapture-region/ Summary We introduce a performant and robust API for cropping a self-capture video track.

[blink-dev] Re: Intent to Extend Experiment: Region Capture

Prior to pressing "send" I neglected to add the following clarification over the auto-generated content: TAG was positive: "Thank you for bringing this to our attention, and we are happy to see this proposal move forward." They did suggest a change of name (Region Capture -> Tab Region Capture),

[blink-dev] Intent to Ship: Region Capture

Contact emailselada...@chromium.org, mfo...@chromium.org, jop...@chromium.org Explainerhttps://github.com/w3c/mediacapture-region/blob/main/README.md Specificationhttps://w3c.github.io/mediacapture-region/ Summary We introduce a performant and robust API for cropping a self-capture video track.

[blink-dev] Re: Intent to Ship: Region Capture

P.S: Requesting to ship gaplessly. On Monday, March 21, 2022 at 9:13:30 PM UTC+1 Elad Alon wrote: > Contact emailselad...@chromium.org, mfo...@chromium.org, > jop...@chromium.org > > Explainerhttps://github.com/w3c/mediacapture-region/blob/main/README.md > > Specificationhttps://w3c.github.io/me

Re: [blink-dev] Intent to Ship: Capture handle

TAG has just closed this issue as "satisfied" and posted "we are happy to see this move forward." On Thursday, March 10, 2022 at 8:01:59 AM UTC+1 yoav...@chromium.org wrote: > On Wed, Mar 9, 2022 at 11:26 AM 'Elad Alon' via blink-dev < > blin...@chrom

[blink-dev] Re: Intent to Ship: Capture handle

Thank you all! Sorry for not asking originally, but - may we ship *gaplessly*? On Wednesday, March 23, 2022 at 4:34:24 PM UTC+1 mkwst via Chromestatus wrote: > LGTM3. > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this gro

[blink-dev] Re: Intent to Ship: Region Capture

> > It may be better to ask actual web developers regarding the least > confusing option amongst those proposed. The Web-developers I am in contact with are happiest with CropTarget. One of them has mentioned that on issue #18 . Other Web-deve

Re: [blink-dev] Re: Intent to Experiment: Captured Surface Control

7 inclusive. > On 1/17/24 9:09 AM, 'Elad Alon' via blink-dev wrote: > > A quick clarification, btw, that we have a partner in mind that's eager to > start origin trial as soon as m122. > We also heard interest from other parties during Screen Capture CG > meetings.

Re: [blink-dev] Re: Intent to Experiment: Captured Surface Control

Thank you! On Wed, May 8, 2024 at 10:20 PM Chris Harrelson wrote: > Sounds fine to me - consider it renumbered from 124. > > On Wed, May 8, 2024 at 1:13 PM 'Elad Alon' via blink-dev < > blink-dev@chromium.org> wrote: > >> Hello Blink owners, >>

[blink-dev] Re: Intent to Experiment: Element Capture

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 request that seems similar to me was granted

Re: [blink-dev] Re: Intent to Experiment: Element Capture

arify 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. > On 5/10/24 6:44 AM, 'Elad Alon' via blink-dev wrote: > > Hello Blink owners, > > We are asking for a br

Re: [blink-dev] Re: Intent to Experiment: Element Capture

024 at 10:25:03 PM UTC+2 mike...@chromium.org wrote: >>> >>>> 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 wr

[blink-dev] Intent to Experiment: Element Capture

Contact emails elada...@chromium.org Explainer https://github.com/screen-share/element-capture/blob/main/README.md Specification https://screen-share.github.io/element-capture Summary API for capturing a subtree of the DOM. Given a video MediaStreamTrack obtained through pre-existing means

Re: [blink-dev] Intent to Experiment: Element Capture

Hi Mike. I'm asking for m121 to m126 (inclusive). On Monday, November 20, 2023 at 5:29:31 PM UTC+1 mike...@chromium.org wrote: > Hi Elad, > > Can you clarify which milestones you intend to experiment in? > > thanks, > Mike > On 11/20/23 6:40 AM, 'Elad Alon&#x

[blink-dev] Re: Intent to Experiment: Element Capture

Thank you for updating, Jan-Ivar. I have now updated this information in the ChromeStatus entry. I am looking forward to carry on the discussion about your position in your standards-positions GitHub repo, in the Element Capture spec repo, in the Screen Capture CG and in the WebRTC WG. On Monda

[blink-dev] Intent to Experiment: Captured Surface Control

Contact emailselada...@chromium.org Explainer https://github.com/screen-share/captured-surface-control/blob/main/README.md SpecificationTBD, but will be hosted on https://screen-share.github.io/captured-surface-control once produced. For the time being, please refer to the explainer

[blink-dev] Re: Intent to Experiment: Captured Surface Control

A quick clarification, btw, that we have a partner in mind that's eager to start origin trial as soon as m122. We also heard interest from other parties during Screen Capture CG meetings. On Wednesday, January 17, 2024 at 2:47:43 PM UTC+1 Elad Alon wrote: > Contact emailselad...@chromium.org > >

[blink-dev] Intent to Prototype: CapturedMouseEvent

Contact emailselada...@chromium.org Explainerhttps://github.com/screen-share/mouse-events/blob/main/README.md Specificationhttps://screen-share.github.io/mouse-events Design document https://docs.google.com/document/d/1FOvWG9WZlulMI9kEc5X0_sspqgdE28q3DFjeaHTmhGk/edit?usp=sharing&resourcekey=0-sQ

Re: [blink-dev] Ready for Trial: Multi-surface capture with auto-accept (for managed sessions only)

Do you want to work with your screen always being recorded? There are many factors that go into choosing an employer, and some drawbacks can be offset by other benefits. Depending on the opportunities available to me, I could definitely see myself accepting employment at a company which reco

Re: [blink-dev] Intent to Experiment: Capture all screens

Hi Arthur! Using the pre-existing getDisplayMedia(), an application can already gain access to the user's screen and capture content in pop-ups, detect browsing history, etc. - provided the user chooses to capture their (often only) screen. All of the concerns above apply for gDM. Further, any

[blink-dev] Intent to Prototype: Element Capture

Contact emailselada...@chromium.org Explainerhttps://github.com/screen-share/element-capture/blob/main/README.md Specificationhttps://screen-share.github.io/element-capture Summary API for capturing a subtree of the DOM. Given a video MediaStreamTrack obtained through pre-existing means to init

[blink-dev] Intent to Prototype: Captured Surface Control

Contact emailselada...@chromium.org Explainer https://github.com/screen-share/captured-surface-control/blob/main/README.md Specificationhttps://screen-share.github.io/captured-surface-control Design docs https://docs.google.com/document/d/10UojDvTJ6ojBEOP7cgBIIaE7WZEfes_Qv1eN3A2A0nM/edit?usp=sha