Re: [blink-dev] Intent to Prototype: Prerendering cross-origin iframes

2025-09-02 Thread Rick Byers
Makes sense to me as an opt-in, thanks for working on this Yoichi! Rick On Tue, Sep 2, 2025 at 12:21 AM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails yoic...@chromium.org > > Explainer > https://github.com/WICG/nav-speculation/blob/main/prerendering-cross-origin-iframes

[blink-dev] Intent to Ship: Local network access restrictions

2025-09-02 Thread Chris Thompson
Contact emails cth...@chromium.org Explainer https://github.com/WICG/local-network-access/blob/main/explainer.md Specification https://wicg.github.io/local-network-access Summary Chrome 141 restricts the ability for sites to make requests to the user's local network, gated behind a permissio

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

2025-09-02 Thread Domenic Denicola
On Wed, Sep 3, 2025 at 9:04 AM 'Daniel Clark' via blink-dev < blink-dev@chromium.org> wrote: > > I believe in WPT we can't have an a.html top-frame navigate to b.html > and check things there. I was not able to find an example in > wpt/navigation-api/. Did I miss anything? > > > > I think it’s c

RE: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

2025-09-02 Thread 'Daniel Clark' via blink-dev
> I believe in WPT we can't have an a.html top-frame navigate to b.html and > check things there. I was not able to find an example in > wpt/navigation-api/. Did I miss anything? I think it’s correct that we can’t test it with top-level navigations, but can we test it for iframe navigations?

[blink-dev] Intent to Extend Experiment: Web Authentication immediate mediation

2025-09-02 Thread Ken Buchanan
Contact emailske...@chromium.org, deri...@google.com Explainer https://github.com/w3c/webauthn/wiki/Explainer:-WebAuthn-immediate-mediation Specificationhttps://github.com/w3c/webauthn/pull/2291 Design docs https://github.com/w3c/webauthn/wiki/Explainer:-WebAuthn-immediate-mediation Summary A

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

2025-09-02 Thread Helmut Januschka
It's relanded now with a feature flag! Thanks to everyone involved, and sorry for the troubles! Helmut Januschka schrieb am Dienstag, 2. September 2025 um 11:00:20 UTC+2: > the revert was back-merged into 140, and i am working on a reland here: > http://crrev.com/c/6898599 with feature flag aro

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

2025-09-02 Thread Mustaq Ahmed
On Thu, Aug 28, 2025 at 9:45 PM Daniel Clark wrote: > *> Gecko*: Positive ( > https://github.com/WICG/view-transitions/issues/239#issuecomment-2851155373 > ) > *> WebKit*: Positive ( > https://github.com/whatwg/html/issues/11328#:~:text=anne%3A%20sounds%20good.%20i%20dont%20think%20we%20will%20re

Re: [EXTERNAL] Re: [blink-dev] Intent to Remove: SwiftShader Fallback

2025-09-02 Thread 'Geoff Lang' via blink-dev
Hey, Chrome can roll out features with server-side configurations to do A/B comparisons or fix breakages without re-releasing, that's what's happening here. Starting in 139, some users are opted into the deprecation. More will be opted in over time until 100%. We're considering unblocking llvmpip

Re: [blink-dev] [Intent to Prototype] Layout Instability Attribution in CSS Pixels

2025-09-02 Thread Ane Diaz De Tuesta
Hello, I’ve addressed the comments on my review. As mentioned in one of them, I’ve had some difficulties running tests locally due to issues with my machine. I think it would be best to run try jobs to identify any remaining modifications needed before the CL can be merged. Could you please r

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

2025-09-02 Thread Helmut Januschka
the revert was back-merged into 140, and i am working on a reland here: http://crrev.com/c/6898599 with feature flag around the change. yoav...@chromium.org schrieb am Freitag, 29. August 2025 um 05:40:48 UTC+2: > On Thu, Aug 28, 2025 at 10:25 PM Krishna Govind wrote: > >> Thank you, any impact