Re: [blink-dev] Intent to Experiment: fetchLater API

Yoav, What milestones do you want to run the experiment in? We plan to run the dev trial in 120. When we request an OT, would you recommend us to send another I2E generated on chromestatus entry? Also, can you kick off the other review checks in your chromestatus entry? Yes, we have kicked off

Re: [blink-dev] Intent to Experiment: Load common payloads from privacy-preserving single-keyed cache

:34:57 PM UTC+5:30 Daisuke Enomoto wrote: > >> Hello >> >> >> Apologies for the confusion! The list of the top 100 pervasive payloads >>> for use in the experiment is pending internal reviews and will be >>> shared on this thread upon approval. >> &

Re: [blink-dev] Intent to Deprecate: Deprecate unload event

Hi Rick, Thank you for your review and feedback. On the enterprise engagement, we have informed them about these upcoming planned changes back in March and have continued the engagement with them to ensure enterprise visibility

[blink-dev] Intent to extend experimentation: Back/forward cache NotRestoredReason API

We would like to extend the origin trial for 3 additional milestones, with the extension starting in 112 continuing through 114. The initial experiment was approved for the OT running from 109 through 111. Contact emails yu...@google.com, yu...@chromium.org, fer...@chromium.org Explainer

[blink-dev] Intent to extend experimentation: Permissions-Policy: unload

API owners, We would like to extend the origin trial for 3 additional milestones, with the extension starting in 110 continuing through 112. The initial experiment was approved for the OT running from 107 through 109. Contact emails fer...@chromium.org Explainer

Re: [blink-dev] Intent to Experiment: Permissions-Policy: unload

ng? > > On Mon, Jan 16, 2023 at 9:38 AM Daisuke Enomoto > wrote: > >> Hi, API owners, >> >> We had requested this Origin Trial to be run for 3 milestones, >> specifically from 107 to 109. This was previously approved. We sent the >> original r

Re: [blink-dev] Intent to Experiment: Permissions-Policy: unload

Hi, API owners, We had requested this Origin Trial to be run for 3 milestones, specifically from 107 to 109. This was previously approved. We sent the original request without realizing the Origin Trial guideline

Re: [blink-dev] Intent to Experiment: Declarative Beacon API

Thank you for your understanding. We'll update the thread as soon as we have clarity on API design and experiment timeline. On Tue, Jun 28, 2022 at 9:38 PM Mike Taylor wrote: > Sounds good - we'll consider this Intent paused until we hear otherwise. > > On 6/27/22 10:14 PM, Daisuk

Re: [blink-dev] Intent to Experiment: Declarative Beacon API

Joe, the API is behind the flag "PendingBeaconAPI". Mike, we came to discuss the new ideas of API design after we sent this I2E. We will update the I2E thread when we have clarity on the design discussion and the timeline when an experiment can start. Caleb, thank you for filing an issue. On

Re: [blink-dev] Intent to Experiment: Load common payloads from privacy-preserving single-keyed cache

gmail.com> wrote: > >> The summary says "payload list included below" - I can't find it >> though... is the list included in one of the links? >> >> On Tuesday, April 26, 2022 at 4:03:11 PM UTC+3 mike...@chromium.org >> wrote: >> >>>

Re: [blink-dev] Re: Intent to Ship: Subresource loading with Web Bundles

Hi Joe, This feature is shipping in 104. I updated the chromestatus entry. Thanks for pinging. On Tue, Jun 7, 2022 at 12:18 AM Joe Medley wrote: > Is this shipping in 105? Please add that to the status entry. > Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | >

Re: [blink-dev] Intent to Extend Origin Trial: Subresource loading with Web Bundles

I would like to make it clear that the previous OT has expired in M101 and it's not enabled in M102. So this intent is to enable it back for 103 through 104. Daisuke On Wed, May 25, 2022 at 12:30 PM Daisuke Enomoto wrote: > Contact emails > > hay...@chromium.org, denom...@chr

[blink-dev] Intent to Extend Origin Trial: Subresource loading with Web Bundles

Contact emails hay...@chromium.org, denom...@chromium.org Explainer https://github.com/WICG/webpackage/blob/master/explainers/subresource-loading.md Specification https://wicg.github.io/webpackage/subresource-loading.html Design docs

Re: [blink-dev] Re: Intent to Ship: Subresource loading with Web Bundles

Hello I am sharing the feedback from the Origin Trial with 12 participants: - 10 of them responded "Extremely likely" to "How likely are you to keep using this feature?" - Qualitative feedback: - "I'm very excited about the CSP interpretation change rolling out in M92"

Re: [blink-dev] Intent to Experiment: Load common payloads from privacy-preserving single-keyed cache

ley | Technical Writer, Chrome DevRel | jmed...@google.com | > 816-678-7195 > *If an API's not documented it doesn't exist.* > > > On Sun, May 1, 2022 at 5:56 PM Daisuke Enomoto > wrote: > >> Hi Joe, >> >> CacheTransparancy is the feature name we use for the

Re: [blink-dev] Intent to Experiment: Load common payloads from privacy-preserving single-keyed cache

ngle-keyed cache), except for >>>> those in the experimental group. >>>> >>>> On Wed, 27 Apr 2022 at 00:50, Joe Medley wrote: >>>> >>>>> What is an 'off-by-default experiment'? Is that a dev trial flag? >>>>> Joe Medle

Re: [blink-dev] Re: Intent to Remove: HTTP/2 and gQUIC server push

ss >>>> don't generate differentiate serving based on the route since the routing >>>> of the application is generally managed in the frontend. >>>> So for Single Page Application to managed server push not global to all >>>> route it will more complex

Re: [blink-dev] Intent to Experiment: Load common payloads from privacy-preserving single-keyed cache

timeline of the experiment? Would it begin in M103? I > have concerns about interactions with the current double-key experiment > <https://groups.google.com/a/chromium.org/g/blink-dev/c/WQtp7Ixd1RU> > we're running for Network State Partitioning in M101 and M102. > > On 4/26/22

Re: [blink-dev] Intent to Ship: Early Hints preload/preconnect during Navigation

Hi Any other questions or concerns? Thanks! On Thu, Apr 21, 2022 at 5:23 PM Kenichi Ishibashi wrote: > Hi Yoav, > > On Thu, Apr 21, 2022 at 3:26 PM Yoav Weiss wrote: > >> >> >> On Thu, Apr 21, 2022 at 4:13 AM Kenichi Ishibashi >> wrote: >> >>> Contact emails >>> >>> ba...@chromium.org,

[blink-dev] Intent to Experiment: Load common payloads from privacy-preserving single-keyed cache

Contact emails ri...@chromium.org, nidhij...@chromium.org, denom...@chromium.org Explainer https://docs.google.com/document/d/1pvaMg7J5beBXD7trzHJH_MDULc_wRHLx40MFYAmjknE/edit Specification N/A (because there are no web-exposed changes) Summary This limited experiment measures how much

Re: [blink-dev] Re: Intent to Remove: HTTP/2 and gQUIC server push

Hello, We conducted an experiment for Early Hints (chromestatus ) with partners in Q3 - Q4, 2021. The experiment data suggests that the performance impact is highly positive. Based on these insights, we are confident that Early Hints will be a

[blink-dev] Intent to Extend Origin Trial: Subresource loading with Web Bundles

Contact emails hay...@chromium.org, denom...@chromium.org Explainer https://github.com/WICG/webpackage/blob/master/explainers/subresource-loading.md Specification Design docs

Re: [blink-dev] Re: [RESPONSE REQUESTED] What's in Chrome 96?

Hello Joe, We decided to land the shipping CLs after addressing TAG review comments, so WebTransport won't ship in M96. There are two items currently not on your list: Back-forward cache on Android