[blink-dev] MakeFromStream is not available in Canvaskit

Hi, In C++,I am trying to read a .skp file as SKPicture as below const char* skpFilePath = "layer_0.skp"; SkFILEStream stream(skpFilePath); sk_sp skPicture =SkPicture::MakeFromStream(); canvas->drawPicture(skPicture.get()); This C++ code works fine. I want to do this in browser. I believe skia

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

I've published the spec PR. Since I can't update the links in the original comment of this thread, I'd like to link the updated explainer here for visibility. pointer-event-extensions/pointer-event-device-id-explainer.md at main · WICG/pointer-event-extensions (github.com)

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

A non-blocking comment: now that the syntax has been changed I think it would be great if you could update the Explainer and the Mozilla and WebKit requests-for-position to reduce potential for confusion. Also, is there a reason the spec PR is still in Draft status? Could it be published so

Re: [blink-dev] Intent to Ship: Tabbed web apps

We don't have an objection to this feature existing - it's actually currently in our backlog. But it is very low in our priority list. While we can review patches, we will not be able to dedicate resources for consultation or maintenance. On Wed, May 8, 2024 at 9:19 AM Brett Wilson wrote: > On

Re: [blink-dev] Running WebGPU on Amazon EC2 Windows instance

Hi Wenhan, Would you join https://groups.google.com/a/chromium.org/g/graphics-dev and post your question there? Several Microsoft colleagues are on that list and may be able to confirm support. -Ken On Wed, May 8, 2024 at 11:46 AM wenhan chong wrote: > Thanks François, > I am not able to

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

Contact emails m...@chromium.org, fugu-...@chromium.org Explainer https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture Specification https://fullscreen.spec.whatwg.org/#dom-element-requestfullscreen Design docs

[blink-dev] Intent to Ship: Stop modifying author-defined selection colors

Contact emailsschen...@chromium.org ExplainerNone Specificationhttps://www.w3.org/TR/css-pseudo-4/#highlight-selectors SummaryChromium currently checks all selection highlight colors against the text color and inverts the highlight color if it matches the text. Hence, author-defined ::selection

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

This is ready for another review :) -- 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit

[blink-dev] Re: Intent to Prototype: Link rel=payment to support push payments

WICG proposal was sent out at https://github.com/WICG/proposals/issues/150 On Wed, May 8, 2024 at 11:03 AM Junhui He wrote: > Contact emailsaneesh...@google.com, junhu...@google.com > > Explainer > https://github.com/aneeshali/paymentlink/blob/main/docs/explainer.md > > Summary > > Adds support

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, >> >> We are asking that the OT period on this

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

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, > > We are asking that the OT period on this experiment be shifted, and > instead of the originally requested period of m122-m127

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

Hello Blink owners, We are asking that the OT period on this experiment be shifted, and instead of the originally requested period of m122-m127 (inclusive), we consider it retroactively as m124-m129 (inclusive). As of the time of writing, there has only ever been one active OT participant

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

This feature has Privacy, Security, Enterprise, and Debuggability approvals. Webkit gave a positive signal. Any objections or questions from the API owners? On Wed, May 1, 2024 at 4:26 PM Eugene Zemtsov wrote: > I've filed issues for TAG review and firefox and webkit positions. > > > Have

Re: [blink-dev] Running WebGPU on Amazon EC2 Windows instance

Thanks François, I am not able to follow the steps completely because they are using Linux instances while I am trying to run WebGPU on Windows Server 2022. Nevertheless, I installed nvidia drivers and vulkan runtime for Windows but Chrome is still unable to detect the GPU. Does Chrome on

[blink-dev] Intent to Prototype: Link rel=payment to support push payments

Contact emailsaneesh...@google.com, junhu...@google.com Explainer https://github.com/aneeshali/paymentlink/blob/main/docs/explainer.md Summary Adds support for as a hint that the browser should notify registered payment clients about a pending push payment. When Blink encounters this HTML

Re: [blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

On 5/8/24 11:30 AM, 'Liam Brady' via blink-dev wrote: Contact emails lbr...@google.com , shivani...@chromium.org , jkar...@chromium.org Explainer(s) https://github.com/WICG/turtledove/pull/1134

Re: [blink-dev] Re: Intent to Ship: Document picture-in-picture: propagate user activation

LGTM3 On 5/8/24 11:56 AM, Daniel Bratell wrote: LGTM2 /Daniel On 2024-05-08 17:11, Yoav Weiss (@Shopify) wrote: LGTM1 On Tuesday, May 7, 2024 at 11:33:01 PM UTC+2 Tommy Steimel wrote: Contact emails stei...@chromium.org, liber...@chromium.org

Re: [blink-dev] Intent to Ship: Tabbed web apps

On Wed, May 8, 2024 at 8:39 AM Alex Russell wrote: > I'm happy for this to be CrOS first, but would like to unpack Brett's > statement above a bit. If we (MSFT) were to polish this up for Windows, > would patches for that be accepted? > I can't speak for the browser team. But my current

[blink-dev] Re: Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

This change would impact the ability of first parties to regulate and prevent reportEvent beacons. Although this requires mutual opt-in, I expect scenarios to eventually come up where a site owner wants to allow cross-origin reportEvent only for certain origins. On Wednesday, May 8, 2024 at

Re: [blink-dev] Re: Intent to Ship: Document picture-in-picture: propagate user activation

LGTM2 /Daniel On 2024-05-08 17:11, Yoav Weiss (@Shopify) wrote: LGTM1 On Tuesday, May 7, 2024 at 11:33:01 PM UTC+2 Tommy Steimel wrote: Contact emails stei...@chromium.org, liber...@chromium.org Explainer None

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

Hey Guido, This is a cool feature! The Milestones section shows that an OT was run; is there a summary someplace of what we learned from the OT? Best, Alex On Thursday, May 2, 2024 at 4:40:31 AM UTC-7 Guido Urdaneta wrote: > Contact emails...@chromium.org, gui...@chromium.org,

Re: [blink-dev] Intent to Ship: Tabbed web apps

I'm happy for this to be CrOS first, but would like to unpack Brett's statement above a bit. If we (MSFT) were to polish this up for Windows, would patches for that be accepted? On Tuesday, May 7, 2024 at 6:25:26 PM UTC-7 Matt Giuca wrote: > Hi Yoav, > > The API was specifically designed to

[blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

Contact emails lbr...@google.com, shivani...@chromium.org, jkar...@chromium.org Explainer(s) https://github.com/WICG/turtledove/pull/1134 Spec(s) https://github.com/WICG/fenced-frame/pull/152 Summary Ad frames (both fenced frames and urn-iframes) created through a Protected Audience

Re: [blink-dev] Intent to Ship: CSSPageRule to inherit from CSSGroupingRule

On 5/8/24 3:37 AM, Morten Stenshorne wrote: Interoperability and Compatibility Low risk. The one possible issue is if an author uses "instanceof CSSGroupingRule" or "instanceof CSSRule" with a page rule object and makes incorrect assumptions based on that. However, given that this

[blink-dev] Re: Intent to Ship: Document picture-in-picture: propagate user activation

LGTM1 On Tuesday, May 7, 2024 at 11:33:01 PM UTC+2 Tommy Steimel wrote: > Contact emailsstei...@chromium.org, liber...@chromium.org > > ExplainerNone > > Specificationhttps://github.com/WICG/document-picture-in-picture/pull/117 > > Design docs > >

[blink-dev] Intent to Ship: CSSPageRule to inherit from CSSGroupingRule

Contact emailsmsten...@chromium.org ExplainerNone Specificationhttps://drafts.csswg.org/cssom/#the-csspagerule-interface Summary Let CSSPageRule inherit from CSSGroupingRule instead of CSSRule. The spec [1] says that the CSSPageRule interface should inherit from CSSGroupingRule, but Blink