Re: [blink-dev] Intent to Ship: Partitioning Storage, Service Workers, and Communication APIs

Is your application running script in the top level context? Since the deprecation trial is implemented as a third-party origin trial, you may be able to sign up as a third party. On Tue, Aug 22, 2023, 23:48 Junji Genesys wrote: > Hello Kyra, > > Thank you for communicating about the rollout

Re: [blink-dev] PSA: Adjacent CDATA sections in XML documents will now be merged

Thanks for digging into this. Given your investigation, I agree that a PSA+flag is sufficient here. On Tue, Aug 22, 2023, 23:08 David Bokan wrote: > Apologies, I wasn't aware the PSA guidance has changed. I've created > https://chromestatus.com/feature/5168429241204736 to track the change. > >

Re: [blink-dev] Intent to Ship: Partitioning Storage, Service Workers, and Communication APIs

Hello Kyra, Thank you for communicating about the rollout plan for the storage partitioning. We've found that the new storage partitioning behavior has impacted our product, which is a web client application embedded in an iframe inside Salesforce and provides call center agents functionality

Re: [blink-dev] PSA: Adjacent CDATA sections in XML documents will now be merged

Apologies, I wasn't aware the PSA guidance has changed. I've created https://chromestatus.com/feature/5168429241204736 to track the change. As to an intent, I believed the breakage risk to be small so thought PSA was sufficient. I think so since we already can perform this kind of merge (from

[blink-dev] Re: Intent to Prototype And Ship: Allow transferring ArrayBuffer into VideoFrame, AudioData, EncodedVideoChunk, EncodedAudioChunk, ImageDecoder constructors

A transfer list is consistent with the approach taken by structuredClone and postMessage . And it's already a part of the WebCodecs spec. On Tue, Aug 22, 2023

Re: [blink-dev] PSA: Ads Relevance and Measurement APIs ramping up

We've reached our milestone for the ~35% ramp-up and intend to continue heading towards ~50% from Wednesday, 23rd August. As before, users need to relaunch Chrome before version updates or incremental API updates take effect. This ramp up includes a mix of different experimental groups. The main

Re: [blink-dev] Re: Intent to Deprecate: Remove "Sanitizer API MVP"

Note that our compat principles say "Generally we avoid breaking any use cases which cannot be shown to have a reasonable alternate implementation". While 0.00492% is tiny, it's still

Re: [blink-dev] Intent to Ship: Baselines in New TextMetrics API in Canvas

Hi Ashley, Thank you for reviewing! I am trying to launch hanging, alphabetic and ideographic baselines and the issues that you pointed out are related to the "top" baseline. I can look into the top baseline definition afterwards. Yi Xu On Tue, Aug 22, 2023 at 5:59 AM Ashley Gullen wrote: >

Re: [blink-dev] Intent to Ship: Storage Access API with Prompts

LGTM3 On 8/22/23 10:49 AM, Yoav Weiss wrote: LGTM2 On Wed, Aug 16, 2023 at 7:31 PM Chris Harrelson wrote: I agree with Chris F. that it's not worth the disruption to change the name or its location, and that leaving the name as-is, even if suboptimal, is a better outcome for

Re: [blink-dev] How CSS Pseudo Elements are handled

On Mon, Aug 21, 2023 at 4:23 PM kalyani Shinde wrote: > Hi Team, > > I have recently started working with chromium/blink, so quite new to this > code. > I wanted to understand where and how css pseudo elements(e.g > webkit-scrollbar) are handled while applying style to any element. These >

Re: [blink-dev] Intent to Ship: Opaque Response Blocking (ORB, aka CORB++) v0.2

On Tue, Aug 22, 2023 at 5:02 PM Dominic Farolino wrote: > It looks like the spec PR here has been dormant for something like ~9 >> months. Are there any plans to help drive it to the finish line, >> especially given the TODOs listed in the OP? How should we all think about >> whatever work might

Re: [blink-dev] Intent to Ship: Attribution Reporting features (lookback windows, flex-lite)

LGTM2 On Wed, Aug 9, 2023 at 6:55 PM Mike Taylor wrote: > Thanks - the risk seems pretty low from a compat POV. > > LGTM1 > On 8/9/23 12:43 PM, John Delaney wrote: > > > Is this based on metrics you have in front of you, or something else? > Also, what might breakage look like in this

Re: [blink-dev] Intent to Ship: Opaque Response Blocking (ORB, aka CORB++) v0.2

> > It looks like the spec PR here has been dormant for something like ~9 > months. Are there any plans to help drive it to the finish line, > especially given the TODOs listed in the OP? How should we all think about > whatever work might remain there, and possibly deviate from what Chrome >

Re: [blink-dev] Intent to Ship: Storage Access API with Prompts

LGTM2 On Wed, Aug 16, 2023 at 7:31 PM Chris Harrelson wrote: > I agree with Chris F. that it's not worth the disruption to change the > name or its location, and that leaving the name as-is, even if suboptimal, > is a better outcome for web developers. > > LGTM1 > > On Wed, Aug 16, 2023 at 9:37 

Re: [blink-dev] Intent to Ship: Opaque Response Blocking (ORB, aka CORB++) v0.2

LGTM3 On 8/22/23 10:37 AM, Yoav Weiss wrote: LGTM2 On Wed, Aug 16, 2023 at 7:23 PM Chris Harrelson wrote: LGTM1 to turn it on in M118 beta and report back to this group about use counter results/bugs reported on beta before it reaches stable. On Fri, Aug 11, 2023 at 2:50 

Re: [blink-dev] Intent to Ship: HTML search element

LGTM3 On Tue, Aug 22, 2023, 7:32 AM Mike Taylor wrote: > LGTM2 > On 8/22/23 10:29 AM, Yoav Weiss wrote: > > LGTM1 > > Thanks for catching us up here! :) > > > On Thu, Aug 17, 2023 at 5:31 AM Vladimir Levin > wrote: > >> >> >> On Wed, Aug 16, 2023 at 4:37 PM Joey Arhar wrote: >> >>> Contact

Re: [blink-dev] Intent to Ship: Opaque Response Blocking (ORB, aka CORB++) v0.2

LGTM2 On Wed, Aug 16, 2023 at 7:23 PM Chris Harrelson wrote: > LGTM1 to turn it on in M118 beta and report back to this group about use > counter results/bugs reported on beta before it reaches stable. > > On Fri, Aug 11, 2023 at 2:50 AM 'Daniel Vogelheim' via blink-dev < >

[blink-dev] Re: Intent to Prototype And Ship: Allow transferring ArrayBuffer into VideoFrame, AudioData, EncodedVideoChunk, EncodedAudioChunk, ImageDecoder constructors

On Tuesday, August 22, 2023 at 11:08:24 AM UTC+2 Jonathan Hao wrote: Hi Eugene, Just to double check. Once an ArrayBuffer is transferred and detached, any further access will result in some sort of TypeError, right? Thanks, Jonathan On Wednesday, August 16, 2023 at 10:22:00 PM UTC+1 Eugene

Re: [blink-dev] Intent to Ship: HTML search element

LGTM2 On 8/22/23 10:29 AM, Yoav Weiss wrote: LGTM1 Thanks for catching us up here! :) On Thu, Aug 17, 2023 at 5:31 AM Vladimir Levin wrote: On Wed, Aug 16, 2023 at 4:37 PM Joey Arhar wrote: Contact emails jar...@chromium.org

Re: [blink-dev] Intent to Implement & Ship: AudioEncoderConfig.bitrateMode

LGTM2 On 8/22/23 10:10 AM, Yoav Weiss wrote: LGTM1. Mirroring video codecs makes sense. Glad to see Mozilla being supportive. On Thu, Aug 17, 2023 at 8:51 PM 'Thomas Guilbert' via blink-dev wrote: Contact emails tguilb...@google.com Explainer None

Re: [blink-dev] Intent to Ship: HTML search element

LGTM1 Thanks for catching us up here! :) On Thu, Aug 17, 2023 at 5:31 AM Vladimir Levin wrote: > > > On Wed, Aug 16, 2023 at 4:37 PM Joey Arhar wrote: > >> Contact emailsjar...@chromium.org >> >> ExplainerNone >> >> Specification >>

Re: [blink-dev] Intent to Ship: Detect UA Transitions on same-document Navigations

LGTM3 Thanks for the clarification! On Tue, Aug 22, 2023 at 4:16 PM 'Khushal Sagar' via blink-dev < blink-dev@chromium.org> wrote: > Clarifying since the explainer mentions 2 APIs. This intent is limited to > a boolean so sites can detect whether there is a UA transition and suppress > their

Re: [blink-dev] Intent to Ship: Detect UA Transitions on same-document Navigations

Clarifying since the explainer mentions 2 APIs. This intent is limited to a boolean so sites can detect whether there is a UA transition and suppress their custom transition. We've paused work on an API to let authors disable UA transitions. Community feedback (see TAG review here

Re: [blink-dev] Intent to Implement & Ship: AudioEncoderConfig.bitrateMode

LGTM1. Mirroring video codecs makes sense. Glad to see Mozilla being supportive. On Thu, Aug 17, 2023 at 8:51 PM 'Thomas Guilbert' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > > tguilb...@google.com > > Explainer > > None > > Specification > >

Re: [blink-dev] Re: Intent to Deprecate: Remove "Sanitizer API MVP"

LGTM2 On Mon, Aug 21, 2023 at 6:17 PM Chris Harrelson wrote: > LGTM1 to remove in favor of a revised, interoperable AIP in the future. > > On Mon, Aug 21, 2023 at 6:38 AM 'Daniel Vogelheim' via blink-dev < > blink-dev@chromium.org> wrote: > >> Hi Luke & Thomas, >> >> On Wed, Aug 16, 2023 at

Re: [blink-dev] Intent to Ship: Baselines in New TextMetrics API in Canvas

There is still this open issue about inconsistent TextMetrics measurements across browsers: https://bugs.chromium.org/p/chromium/issues/detail?id=1183752 I think it may involve this unresolved spec issue: https://github.com/whatwg/html/issues/6731 This is causing us constant annoying

[blink-dev] Re: Intent to Prototype And Ship: Allow transferring ArrayBuffer into VideoFrame, AudioData, EncodedVideoChunk, EncodedAudioChunk, ImageDecoder constructors

Hi Eugene, Just to double check. Once an ArrayBuffer is transferred and detached, any further access will result in some sort of TypeError, right? Thanks, Jonathan On Wednesday, August 16, 2023 at 10:22:00 PM UTC+1 Eugene Zemtsov wrote: > Contact emailsezemt...@google.com > >

Re: [blink-dev] PSA: Adjacent CDATA sections in XML documents will now be merged

In particular, we recently clarified our process RE changes to existing behavior . It'd be good to answer the questions in "step 2" to understand if the breakage potential here is very unlikely. On Tue, Aug 22, 2023 at 8:29 AM

Re: [blink-dev] PSA: Adjacent CDATA sections in XML documents will now be merged

Given that this presents a Web compat risk, is there a ChromeStatus entry + Intent thread for this? On Mon, Aug 21, 2023 at 7:05 PM David Bokan wrote: > Hi blink-dev, > > I just landed https://crrev.com/f848cbce89b422 which will cause an XML > document to merge sibling CDATA section nodes into