Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

The exact steps of the sanitization process isn't specified anywhere since it's very fluid and also subject to change based on the outcome of the Sanitizer API proposal. Since the HTML format already uses this sanitizer, we decided to use it for SVG format as well. This was also proposed by the

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

On Tue, Feb 27, 2024 at 10:40 PM Anupam Snigdha wrote: > We're using the same sanitizer that HTML format uses to produce a fragment > with styles inlined. This is also the same sanitization process used in > paste operation(ctrl+V). > OK, so that's the one specified in https://github.com/w3c/cli

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

We're using the same sanitizer that HTML format uses to produce a fragment with styles inlined. This is also the same sanitization process used in paste operation(ctrl+V). From: Yoav Weiss (@Shopify) Sent: Tuesday, February 27, 2024 1:30 PM To: Anupam Snigdha Cc

[blink-dev] Re: Web-Facing Change PSA: Interoperable mousedown event cancellation in iframe

Hi all! Thanks for posting this discussion. My name is Tai, and I'm an engineer at Webflow. Just wanted to comment that this change triggered a regression in our Designer editor. Our application architecture involves rendering the design editor within an iframe and surrounding it with tools i

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

On Tue, Feb 27, 2024 at 10:18 PM Anupam Snigdha wrote: > I noticed that the tests here are marked as "tentative". Is the > sanitizer part of this specified? > > Since there is no consensus on the clipboard sanitization, the tests are > marked as tentative for now. We had discussions >

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

I noticed that the tests here are marked as "tentative". Is the sanitizer part of this specified? Since there is no consensus on the clipboard sanitization, the tests are marked as tentative for now. We had discussions

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

On Fri, Feb 23, 2024 at 7:40 PM Daniel Bratell wrote: > LGTM > > Not sure if it's LGTM2 or LGTM4 since that depends on if the 2021 LGTMS > still apply, but this still seems ready to ship. > > /Daniel > On 2024-02-23 19:14, Chris Harrelson wrote: > > My LGTM still stands, and have recorded it in t

Re: [blink-dev] Intent to Prototype and Ship: Standardized CSS zoom

On Mon, Feb 26, 2024 at 7:36 PM Mike Taylor wrote: > Thanks for the feedback Noam - would you mind filing a bug at > crbug.com/new that contains some steps to reproduce the breakage, and > possibly some affected codepaths and report back here? Agree that breaking > Excel is not a great outcome. >

Re: [blink-dev] Intent to Experiment: FedCM multi IDP in single get() call

LGTM to experiment M124-M128 inclusive On Tue, Feb 27, 2024 at 4:16 PM Nicolás Peña wrote: > Done > > On Monday, February 26, 2024 at 7:55:09 PM UTC-5 Mike Taylor wrote: > >> Could you please request reviews for the privacy/security/debuggability >> review gates in your chromestatus entry? >> On

Re: [blink-dev] Intent to Ship: CSS paint-order for non-SVG text

I removed 'tentative' from the test name (PR ). On Thu, Feb 15, 2024 at 6:15 PM Mike Taylor wrote: > LGTM3, with the same conditions from Chris. > On 2/15/24 6:15 PM, Chris Harrelson wrote: > > LGTM2, conditioned on also making the tests Rego

Re: [blink-dev] Intent to Experiment: FedCM multi IDP in single get() call

Done On Monday, February 26, 2024 at 7:55:09 PM UTC-5 Mike Taylor wrote: > Could you please request reviews for the privacy/security/debuggability > review gates in your chromestatus entry? > On 2/21/24 3:21 PM, Nicolás Peña wrote: > > Contact emails > > n...@chromium.org > > Explainer > > The

Re: [blink-dev] Intent to Experiment: Add JavaScript timer wake up alignment for unimportant cross-origin frames

fdoray@ launched this trial since Nov 2023, at first canary/dev, and then beta, 1% stable. The experiments show statistically improvements to CPU time on navigation, page load time and input delay. So we are requesting to experiment on 50% stable as next step. Actually the feature should be in