Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

On Wed, 6 Dec 2023 at 13:55, Fergal Daly wrote: > On Wed, 6 Dec 2023 at 12:29, Vladimir Levin wrote: > >> Thank you for the update! >> >> This is a good write up. One comment / question below >> >> From the doc: >> > Note that the pageshow event will trigger before the page is rendered >> for th

Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

On Wed, 6 Dec 2023 at 12:29, Vladimir Levin wrote: > Thank you for the update! > > This is a good write up. One comment / question below > > From the doc: > > Note that the pageshow event will trigger before the page is rendered > for the first time upon being restored from a back/forward navigat

Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

Thank you for the update! This is a good write up. One comment / question below >From the doc: > Note that the pageshow event will trigger before the page is rendered for the first time upon being restored from a back/forward navigation, which guarantees that your login state check will let you r

Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

We now have a published doc that covers best practices for BFCache/CCNS (and much more) during logout. Please let us know if you have any feedback on it. We will proceed with cautiously rolling out this change. Thanks everyone, F On Thu, 16 Nov

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

FYI, we are also planning to provide a grace period for sites registered and approved for the deprecation trial to give them time to deploy trial tokens. See this updated section of the blog post: https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%2

Re: [blink-dev] Intent to Ship: Interoperable mousemove default action

Hey Mustaq, Thanks for pushing to get this long-time interop issue addressed! I assume cancelling the mousedown (but not the mousemove) still prevents selection and drag-and-drop in all browsers, is that right? That's the pattern I'd expect is most common. Also, what's the behavior of pointermove f

Re: [blink-dev] Intent to Ship: Lazy load scroll margin

Well, that is debatable... Because the image is 0x0 before it is loaded and centered, it is technically not in the viewport, but I am not sure why it would be 0x0. I am changing the original snippet to this (untested, just more like what I have) - That extraneous seems to cause this... I need

Re: [blink-dev] Intent to Ship: Auto Sizes for Lazy Loaded Images with Srcset

LGTM2 On 12/5/23 2:33 PM, Rick Byers wrote: Nice! LGTM1 On Fri, Dec 1, 2023 at 2:08 AM Traian Captan wrote: Contact emails tcap...@chromium.org Explainer https://github.com/whatwg/html/issues/4654 Specification https://html.spec.whatwg.o

Re: [blink-dev] Intent to Ship: Attribution Reporting Features (Reduced Aggregate Delays, Event-Level Report Epsilon Field, Reserved Keys)

LGTM2 On 12/5/23 2:29 PM, Rick Byers wrote: LGTM1 On the interoperability risks front I see there's still no official position on the API from Mozilla or WebKit . On Thu, N

Re: [blink-dev] Intent to Ship: URLPattern: hasRegExpGroups

LGTM2 On 12/5/23 2:23 PM, Rick Byers wrote: Yeah looks pretty trivial, thanks for the improvement! LGTM1 On Wed, Nov 29, 2023 at 9:34 PM Jeremy Roman wrote: Contact emails jbro...@chromium.org Explainer None Specification https://urlpatt

Re: [blink-dev] Re: Intent to Ship: Async Clipboard API: Read unsanitized HTML format

LGTM3 On 12/5/23 1:57 PM, 'Rick Byers' via blink-dev wrote: By the way, for others trying to follow the history, the correct link to the original thread on this is https://groups.google.com/a/chromium.org/g/blink-dev/c/oiPCXHy9kRE/m/YS2sxbIQAAAJ On Tue, Dec 5, 2023 at 1:56 PM Rick Byers wrot

[blink-dev] As a web feature author, which Chrome Status changes would help you?

Hi Blink contributors, Chrome Status has spent the last year implementing support for approval gates, but now it's time to increase focus on things that will help feature authors work their way through the process. What would help you? I've collected an initial set of relevant bugs under the for-

Re: [blink-dev] Intent to Ship: Auto Sizes for Lazy Loaded Images with Srcset

Nice! LGTM1 On Fri, Dec 1, 2023 at 2:08 AM Traian Captan wrote: > Contact emailstcap...@chromium.org > > Explainerhttps://github.com/whatwg/html/issues/4654 > > Specificationhttps://html.spec.whatwg.org/#sizes-attributes > > Summary > > Auto Sizes allows developers to set the sizes attribute to

Re: [blink-dev] Intent to Ship: Attribution Reporting Features (Reduced Aggregate Delays, Event-Level Report Epsilon Field, Reserved Keys)

LGTM1 On the interoperability risks front I see there's still no official position on the API from Mozilla or WebKit . On Thu, Nov 30, 2023 at 3:38 PM 'Akash Nadan' via blink-dev

[blink-dev] PSA: chrome_wpt_tests has been added to CI/CQ

Hello Fellow Developers! This email is a PSA for running Web platform tests against Chrome on CI/CQ. What? - A new test suite “chrome_wpt_tests” has been added to the CI/CQ, which will run web platform tests against Chrome. Why? - Data has shown about 2% of WPTs have differ

Re: [blink-dev] Intent to Ship: URLPattern: hasRegExpGroups

Yeah looks pretty trivial, thanks for the improvement! LGTM1 On Wed, Nov 29, 2023 at 9:34 PM Jeremy Roman wrote: > Contact emailsjbro...@chromium.org > > ExplainerNone > > Specification > https://urlpattern.spec.whatwg.org/#dom-urlpattern-hasregexpgroups > > Summary > > Allows easy inspection of

Re: [blink-dev] Intent to Extend Experiment: Compute Pressure API

Hi, Can you please request review for the security, privacy and debuggability bits now in the chromestatus tool? Perhaps there's some history somewhere you can point at from the first OT? Otherwise, seems reasonable to extend to me. Rick On Mon, Dec 4, 2023 at 1:59 PM Mandy, Arnaud wrote: > C

Re: [blink-dev] Intent to Ship: Multiple Readers and Writers in File System Access API

LGTM2. Looks like the spec PR is reviewed but just blocked waiting for input from a 2nd implementor, but Firefox has implemented their support. Can you poke the relevant Firefox folks to see if someone can chime in on the spec PR to help get it landed? But doesn't seem necessary to block this I2S

Re: [blink-dev] Intent to Ship: Extension of WebDriver command for clicking on FedCM dialogs

LGTM2 On Tue, Dec 5, 2023 at 12:31 PM Mike Taylor wrote: > LGTM1 > On 12/5/23 3:44 AM, 'Zachary Tan' via blink-dev wrote: > > My mistake - it is indeed without the "k", thanks for double checking. > > On Tue, Dec 5, 2023 at 5:34 PM Domenic Denicola > wrote: > >> >> >> On Tue, Dec 5, 2023 at 3:4

[blink-dev] Re: Intent to Ship: Async Clipboard API: Read unsanitized HTML format

By the way, for others trying to follow the history, the correct link to the original thread on this is https://groups.google.com/a/chromium.org/g/blink-dev/c/oiPCXHy9kRE/m/YS2sxbIQAAAJ On Tue, Dec 5, 2023 at 1:56 PM Rick Byers wrote: > Thanks for getting this cleaned up and clarified, and for g

[blink-dev] Re: Intent to Ship: Async Clipboard API: Read unsanitized HTML format

Thanks for getting this cleaned up and clarified, and for getting the spec PR landed. This now seems quite trivial to me - just extending the existing unsanitized reading capability into an option of the async clipboard API. LGTM2 On Wed, Nov 29, 2023 at 4:39 PM Alex Russell wrote: > Thanks for

Re: [blink-dev] Intent to Ship: Third-party cookie deprecation exemption heuristics

LGTM2 Thank you for putting the extra rigor and effort into trying to specify and align on this behavior, rather than just copy the precedent set by the other two engines in relying on non-standards-track heuristics! It's exactly in these messy real-world examples of web behavior that our principl

Re: [blink-dev] Intent to Ship: Third-party cookie deprecation exemption heuristics

I see this as a critical web compatibility intervention, so LGTM1. It seems like there is some disagreement about spec venue (compat vs fetch/html), but I don't think we need to block on landing given the other browsers shipped their heuristics without specifying in any standards venue. Thanks

Re: [blink-dev] Intent to Ship: Extension of WebDriver command for clicking on FedCM dialogs

LGTM1 On 12/5/23 3:44 AM, 'Zachary Tan' via blink-dev wrote: My mistake - it is indeed without the "k", thanks for double checking. On Tue, Dec 5, 2023 at 5:34 PM Domenic Denicola wrote: On Tue, Dec 5, 2023 at 3:42 PM 'Zachary Tan' via blink-dev wrote: Contact e

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

The deprecation trial is now open for registrations: https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369 Again, please be aware this trial will require a review process as outlined in the blog pos t.

Re: [blink-dev] Intent to Deprecate & Remove: Third-Party Cookies

Good morning all, Our organization is currently re-reviewing the impacts of the third party cookie deprecation now that registration for deprecation trials have been made available. Among our offerings, we provide consulting, hosting, architecture, and development services for customers in the

Re: [blink-dev] Intent to Ship: Extension of WebDriver command for clicking on FedCM dialogs

My mistake - it is indeed without the "k", thanks for double checking. On Tue, Dec 5, 2023 at 5:34 PM Domenic Denicola wrote: > > > On Tue, Dec 5, 2023 at 3:42 PM 'Zachary Tan' via blink-dev < > blink-dev@chromium.org> wrote: > >> Contact emails >> >> tanzach...@chromium.org >> >> Explainer >> >

Re: [blink-dev] Intent to Ship: Extension of WebDriver command for clicking on FedCM dialogs

On Tue, Dec 5, 2023 at 3:42 PM 'Zachary Tan' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > > tanzach...@chromium.org > > Explainer > > None > > Specification > > https://github.com/fedidcg/FedCM/pull/510 > > Design docs > > None > > Summary > > This changes one of our existing