Re: [blink-dev] Intent to Ship: Dispatching click events to captured pointer

2025-02-05 Thread Yoav Weiss (@Shopify)
On Wed, Feb 5, 2025 at 4:11 PM Mustaq Ahmed wrote: > Contact emailsmus...@chromium.org > > Explainerhttps://w3c.github.io/pointerevents/#event-dispatch > > Specificationhttps://w3c.github.io/pointerevents/#event-dispatch > > Summary > > If a pointer is captured while the `pointerup` event is bein

Re: [blink-dev] Android shared workers

2025-02-05 Thread Thomas Danecker
Hello, SharedWorker seems to be the only way to store OAuth 2.0 access tokens securely in browser sessions and share them between tabs. See for example the best practices described here: https://auth0.com/docs/secure/security-guidance/data-security/token-storage Any other solutions (e.g. using

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature: Remove Aggregatable report limit when trigger context ID is non-null

2025-02-05 Thread Nan Lin
Hi Yoav, Thanks for the response. On Wed, Feb 5, 2025 at 11:14 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Tuesday, January 28, 2025 at 8:19:10 PM UTC+1 Akash Nadan wrote: > > Hi Mike, > > Thanks for flagging this. We have requested all of the bits in the > chromestatus en

[blink-dev] Re: Intent to Ship: Private Aggregation API: per-context contribution limits for Shared Storage callers

2025-02-05 Thread Yoav Weiss (@Shopify)
On Tuesday, February 4, 2025 at 9:20:37 PM UTC+1 Dan McArdle wrote: Contact emailsdmcar...@chromium.org Explainerhttps://github.com/patcg-individual-drafts/private- aggregation-api#limiting-the-number-of-contributions-per-report Specificationhttps://github.com/patcg-individual-drafts/private-

[blink-dev] Action required: You're invited to BlinkOn 20 on Apr 7-8!

2025-02-05 Thread BlinkOn Planning Committee
bcc: blink-dev Hi everyone! Register now for BlinkOn 20 in April 2025! Register now to join us for BlinkOn 20 this upcoming April! - Date: April 7-8, 2025 - Time: Tent

Re: [blink-dev] Intent to Ship: Dispatching click events to captured pointer

2025-02-05 Thread Mustaq Ahmed
Hi Mike and Yoav: Let me answer your questions together: *Current behavior in major browsers:* The click target is: - [Chrome] the common ancestor of pointerdown target and *captured* pointerup target. - [Firefox] the actual pointerup target, ignoring capture and pointerdown. - [Safari] the commo

Re: [blink-dev] Intent to Ship: Dispatching click events to captured pointer

2025-02-05 Thread Mike Taylor
On 2/5/25 10:11 AM, Mustaq Ahmed wrote: Contact emails mus...@chromium.org Explainer https://w3c.github.io/pointerevents/#event-dispatch Specification https://w3c.github.io/pointerevents/#event-dispatch Summary If a p

[blink-dev] Intent to Prototype: CSP require-sri-for

2025-02-05 Thread Yoav Weiss (@Shopify)
Contact emailsyoavwe...@chromium.org ExplainerNot yet SpecificationNot yet Summary The `require-sri-for` directive gives developers the ability to assert that every resource of a given type needs to be integrity checked. If a resource of that type is attempted to be loaded without integrity met

[blink-dev] Intent to Ship: Dispatching click events to captured pointer

2025-02-05 Thread Mustaq Ahmed
Contact emailsmus...@chromium.org Explainerhttps://w3c.github.io/pointerevents/#event-dispatch Specificationhttps://w3c.github.io/pointerevents/#event-dispatch Summary If a pointer is captured while the `pointerup` event is being dispatched, the `click` event will be dispatched to the captured

Re: [blink-dev] Re: Intent to Extend Experiment: JavaScript Promise Integration

2025-02-05 Thread Chris Harrelson
LGTM On Wed, Jan 29, 2025 at 3:29 PM 'Deepti Gandluri' via blink-dev < blink-dev@chromium.org> wrote: > Adding to Francis's reply, JSPI has been inherently hard to specify, and > validate security requirements for given that it is somewhat sandwiched > between JS & Wasm. Concretely, since the las

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature: Remove Aggregatable report limit when trigger context ID is non-null

2025-02-05 Thread Yoav Weiss (@Shopify)
On Tuesday, January 28, 2025 at 8:19:10 PM UTC+1 Akash Nadan wrote: Hi Mike, Thanks for flagging this. We have requested all of the bits in the chromestatus entry. Thanks, Akash On Tuesday, January 28, 2025 at 7:17:03 AM UTC-8 Mike Taylor wrote: Please request the various bits in your chrom

Re: [blink-dev] Intent to Ship: Custom data origin in sharedStorage.createWorklet

2025-02-05 Thread Chris Harrelson
LGTM1 On Wed, Jan 29, 2025 at 1:08 PM Josh Karlin wrote: > Contact emailscam...@chromium.org, yao...@chromium.org, > jkar...@chromium.org, saraak...@google.com > > Explainerhttps://github.com/WICG/shared-storage >

Re: [blink-dev] Intent to Ship: Custom data origin in sharedStorage.createWorklet

2025-02-05 Thread Mike Taylor
LGTM2 On 2/5/25 11:15 AM, Chris Harrelson wrote: LGTM1 On Wed, Jan 29, 2025 at 1:08 PM Josh Karlin wrote: Contact emails cam...@chromium.org, yao...@chromium.org, jkar...@chromium.org, saraak...@google.com Explainer https://github.com/WICG/shared-stora

Re: [blink-dev] Intent to Ship: Element Reflection

2025-02-05 Thread 'Dan Clark' via blink-dev
Should this Intent be considered as including ariaOwnsElements ? That was split off into a separate flag from the other

Re: [blink-dev] Intent to Ship: Dispatching click events to captured pointer

2025-02-05 Thread Domenic Denicola
LGTM1. This seems like a valuable movement toward interop on tricky edge-cases, and the team has done a good job with use counters and beta experiments to bound the compat risks. I think Finch can be used as a killswitch if we find that this has some horrible breaking impact that has not yet been d