Re: [blink-dev] Intent to Ship: Multi-argument alt text in CSS Generated Content

LGTM3. It's a bit sad that there's no spec that actually matches the 3/3 shipping implementations, but oh well... Hopefully MDN documentation and the like will fill in that gap. On Wednesday, May 15, 2024 at 6:01:17 AM UTC+9 Chris Harrelson wrote: > LGTM2 > > On Tue, May 14, 2024 at 1:49 PM

Re: [blink-dev] Re: Intent to Ship: WebRTC encoded transform - Constructor with custom Metadata (originally Modify Metadata functions)

LGTM2 On Wednesday, May 15, 2024 at 4:47:32 AM UTC+9 Mike Taylor wrote: > Thanks for the doc. It sounds like the design evolved during the OT based > on fedback from the WG, and at least one partner was satisfied with the > shape and functionality. > > LGTM1 > On 5/14/24 8:05 AM, Guido

Re: [blink-dev] Intent to Ship: Support Video Chapter in MediaMetadata

Hi Jiaming, Per our process , we give the TAG and other vendors at least one month to comment on changes. (This is why it is recommended to start these reviewers earlier, before sending the Intent to Ship.) So it

Re: [blink-dev] Intent to Implement and Ship: Conversion to RGB in VideoFrame.copyTo()

LGTM1. I have a small non-blocking request: update your Chrome Status entry to avoid using ClassName.staticMethod() syntax for what appears to be an instance method. (See e.g. this related discussion and this bug I filed on Chrome Status a year

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

Thanks! I pinged the PR, and hope for some feedback there soon. Feature detection via Permissions API querying seems like a great follow up here, ideally alongside broadened feature availability (i.e. extending user control beyond Isolated Web Apps). On Tue, May 14, 2024 at 1:43 PM Mike Taylor

Re: [blink-dev] Intent to Ship: Support Cross-Origin Shared Storage Worklets

Hi Harley, This is a demo site for the cross-origin worklet: https://shared-storage-cross-origin-worklet-demo.glitch.me Yao On Tue, May 14, 2024 at 12:20 PM Harley Li wrote: > Hello - wondering whether this cross-origin feature reflected in the demo > website

[blink-dev] Intent to Ship: Third-party Cookie Grace Period Opt-Out

Contact emails amal...@chromium.org njeu...@chromium.org wanderv...@chromium.org Explainer https://github.com/explainers-by-googlers/3pcd-grace-period-opt-out Specification Well-known resource specification:

Re: [blink-dev] Intent to Ship: Multi-argument alt text in CSS Generated Content

LGTM2 On Tue, May 14, 2024 at 1:49 PM Mike Taylor wrote: > From what I can tell, this shipped in Firefox a few days ago, and should > be in 127: https://bugzilla.mozilla.org/show_bug.cgi?id=1281158#c26 > > LGTM1 > On 5/13/24 4:15 PM, 'Daniel Clark' via blink-dev wrote: > > *> Gecko: No signal

Re: [blink-dev] Intent to Ship: Multi-argument alt text in CSS Generated Content

From what I can tell, this shipped in Firefox a few days ago, and should be in 127: https://bugzilla.mozilla.org/show_bug.cgi?id=1281158#c26 LGTM1 On 5/13/24 4:15 PM, 'Daniel Clark' via blink-dev wrote: /> Gecko: No signal (https://bugzilla.mozilla.org/show_bug.cgi?id=1281158//)/ /> It's

Re: [blink-dev] Intent to Implement and Ship: Conversion to RGB in VideoFrame.copyTo()

By reading an MDN article that I'll update after the launch. Even now allocationSize() is supposed to be called before copyTo() anyway, to figure out the size of the buffer for the output. (see example 1, example2

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

It would be nice for the PR to be reviewed and approved, even without other stakeholder support. Additionally - the explainer mentions a few options for feature detection. Any progress on that front? Or is it just hypothetical? On 5/9/24 3:04 PM, Mike Wasserman wrote: Sure. I'll note that

Re: [blink-dev] Intent to Implement and Ship: Conversion to RGB in VideoFrame.copyTo()

Ergonomics-wise, it does not seem intuitive to use a method called allocationSize() to feature detect copyTo support, even if the semantics are the same. Besides a very careful reading of the spec, how do we expect developers to know about it? On 5/14/24 4:32 PM, Eugene Zemtsov wrote: In that

Re: [blink-dev] Intent to Implement and Ship: Conversion to RGB in VideoFrame.copyTo()

In that discussion Marcos Cáceres asked for a synchronous way to detect if format conversion is supported. We have a synchronous call allocationSize() that throws an unsupported error in cases where format conversion is not

Re: [blink-dev] Re: Intent to Ship: WebRTC encoded transform - Constructor with custom Metadata (originally Modify Metadata functions)

Thanks for the doc. It sounds like the design evolved during the OT based on fedback from the WG, and at least one partner was satisfied with the shape and functionality. LGTM1 On 5/14/24 8:05 AM, Guido Urdaneta wrote: Here is a doc with feedback from the Origin Trial. There were two

Re: [blink-dev] Intent to Implement and Ship: Conversion to RGB in VideoFrame.copyTo()

I see that WebKit raised an API concern around detectability . In your reply, you said "we should consider...". Has that consideration happened, perhaps as follow-up work? :) On 5/8/24 4:05 PM, Eugene Zemtsov

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

LGTM2 On Tue, May 14, 2024 at 11:36 AM Mike Taylor wrote: > OK - 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. > On 5/14/24 12:08 PM, Elad

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

OK - 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. On 5/14/24 12:08 PM, Elad Alon wrote: I'm asking for a break-off period starting July 1 and

Re: [blink-dev] Intent to Ship: CSS Anchor Positioning

On 5/13/24 15:06, 'Mason Freed' via blink-dev wrote: First, I’d just like to correct the record, for the benefit of the folks who have been working for years on this feature (including lots of outreach), and for everyone following this discussion: [...] Mason, I don't contest any of these

Re: [blink-dev] Intent to Ship: Support Cross-Origin Shared Storage Worklets

Hello - wondering whether this cross-origin feature reflected in the demo website https://shared-storage-demo.web.app/ ? That is, not cross-origin-worklet-select-url-and-verify-data-origin.tentative.https.sub.html

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

I'm asking for a break-off period starting July 1 and ending July 22 (inclusive). That means that the original trial will end on June 30, and be restarted on July 23. This corresponds to breaking the original experiment early during the cycle of what would have otherwise been its final

[blink-dev] Re: Intent to Ship: WebRTC encoded transform - Constructor with custom Metadata (originally Modify Metadata functions)

Here is a doc with feedback from the Origin Trial. There were two registrants reported with a large usage scale. We received feedback from one of them and will update the doc if/when we get feedback from the other one.