blink-dev

The list construction should already be completely objective. I changed the manual origin-owner

This one seems a bit trickier than RWS itself because we have to reason about the risk of code that

I guess the worst case breakage here is just a return to the old world where users who opt-out of

Intent to deprecate and remove Shared Storage Contact emails cam...@chromium.org Explainer https://

Intent to Deprecate and Remove: Protected Audience Contact emails paulj...@chromium.org Explainer

Contact emails ale...@chromium.org Explainer https://github.com/patcg-individual-drafts/private-

Intent to Deprecate and Remove: Attribution Reporting API Contact emails lin...@chromium.org, jkarlin

Intent to Deprecate and Remove: Topics API Contact emails yao...@chromium.org Explainer https://

Sure, let's do this in reverse order: LGTM2 (both Daniel and I have already approved on

LGTM2 The standards positions issues are in a somewhat unusual state, but we've filed them and

LGTM1 The WebKit standards position was only filed yesterday, but this seems straightforward and

Alex, I don't see how this incremental improvement is anything different from other incremental

WebRTC leaks the user's local network IP under the Tor network. Steps to reproduce the problem

LGTM3 On 11/6/25 1:20 pm, Philip Jägenstedt wrote: LGTM2 On Thu, Nov 6, 2025 at 7:14 PM 'Frank

On Sat, Nov 1, 2025 at 2:08 PM optimi zix <opti...@gmail.com> wrote: Well technically XPath

LGTM3 On Thu, Nov 6, 2025 at 6:44 PM Chris Harrelson <chri...@chromium.org> wrote: LGTM2 On

LGTM2 On Thu, Nov 6, 2025 at 1:43 AM 'Divyansh Mangal' via blink-dev <blink-dev@chromium.

Contact emails mike...@chromium.org Explainer https://github.com/WICG/ua-client-hints/blob/main/

Thanks everyone for the review. As per Rick's comment, I will keep this thread updated. On

Thanks very much for the suggestions! We will look into this issue and follow up the WG discussions

LGTM3 On Wed, Nov 5, 2025 at 5:33 PM Yoav Weiss (@Shopify) <yoav...@chromium.org> wrote:

LGTM3 On Wednesday, November 5, 2025 at 8:08:01 AM UTC-8 Vladimir Levin wrote: That makes sense

On Wed, Nov 5, 2025 at 9:08 AM Ashley Gullen <ash...@scirra.com> wrote: Given that the existing

LGTM3 On Wed, Nov 5, 2025 at 8:41 AM Sebastian Zartner <sebastia...@gmail.com> wrote: For

Summary The renderBlockingStatus flag in Resource Timing allows identification of resources which are

Update: We have unflagged Temporal. Barring any unforeseen issues, this ought to ship in Chrome 144 (

Contact Emails ari...@chromium.org, alex...@google.com, a...@google.com, mike...@chromium.org

Thanks - LGTM to experiment from 143 to 148 inclusive. On 11/4/25 1:37 pm, 'Lia Hiscock' via

If you do not ship a Payment Handler or integrate Payment Request into your website, you can stop

Reading the issue, it looks like they've figured out the issue, which involves iframes and