Re: [blink-dev] Intent to Ship (I2S): Protected Audience

2023-06-30 Thread Paul Jensen
On Fri, Jun 30, 2023 at 5:03 PM Mike Taylor wrote: > On 7/1/23 3:09 AM, Paul Jensen wrote: > > > On Wed, Jun 28, 2023 at 5:33 AM Yoav Weiss wrote: > >> >> >> On Tue, Jun 27, 2023 at 9:54 PM Paul Jensen >> wrote: >> >>> Yoav, >>> >>> Protected Audiences has been fortunate to have a ton of

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

2023-06-30 Thread Mike Taylor
On 7/1/23 3:09 AM, Paul Jensen wrote: On Wed, Jun 28, 2023 at 5:33 AM Yoav Weiss wrote: On Tue, Jun 27, 2023 at 9:54 PM Paul Jensen wrote: Yoav, Protected Audiences has been fortunate to have a ton of design contributions and feedback, but consequently

Re: [blink-dev] Intent to Ship: RFC 7616 Digest auth: Support SHA-256, SHA-512-256 and user hashing

2023-06-30 Thread Deomid "rojer" Ryabkov
ok, added a flag (enabled by default). On Thu, 29 Jun 2023 at 10:21, Rick Byers wrote: > Agreed that given we don't have metrics proving the usage is really rare, > we should err on the side of caution and follow the "all new APIs need a > killswitch" guideline >

Re: [blink-dev] Intent to Remove: CSS property -webkit-highlight

2023-06-30 Thread Stephen Chenney
Thanks Mike for looking up github usage. It does indeed do nothing and the github refs are all -webkit-highlight: none or initial, which I have to assume was also none. We checked many of the http-archive links and they were all the one a11y library usage, all value none. Cheers, Stephen. On

Re: [blink-dev] Intent to Remove: CSS property -webkit-highlight

2023-06-30 Thread Mike Taylor
https://github.com/search?type=code=-webkit-highlight+language%3ACSS=CSS shows this has been used elsewhere (but I guess has just been useless in clank?). That said, LGTM2. On 7/1/23 4:33 AM, Rick Byers wrote: Removing a prefixed API with no behavior should be trivial, thanks for the

Re: [blink-dev] Intent to Remove: CSS property -webkit-highlight

2023-06-30 Thread Rick Byers
Removing a prefixed API with no behavior should be trivial, thanks for the cleanup Stephen :-) However, the UseCounter is surprisingly high with lots of hits in HA: https://chromestatus.com/metrics/css/timeline/popularity/251. Just confirming that you looked at a sample of those hits and found

[blink-dev] Intent to Ship: Inherit Base URL snapshot for about:blank and about:srcdoc, with about:blank inheriting from initiator, not parent.

2023-06-30 Thread W. James MacLean
Intent to Ship: Inherit Base URL snapshot for about:blank and about:srcdoc, with about:blank inheriting from initiator, not parent. Contact emails wjmacl...@chromium.org cr...@chromium.org d...@chromium.org Explainer None Specification https://github.com/whatwg/html/pull/9464 (original

Re: [blink-dev] Intent to Ship (I2S): Protected Audience

2023-06-30 Thread Paul Jensen
On Wed, Jun 28, 2023 at 5:33 AM Yoav Weiss wrote: > > > On Tue, Jun 27, 2023 at 9:54 PM Paul Jensen > wrote: > >> Yoav, >> >> Protected Audiences has been fortunate to have a ton of design >> contributions and feedback, but consequently has a lot of issues filed. We >> try to respond to all

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

2023-06-30 Thread Mike Taylor
LGTM3 On 6/30/23 9:10 PM, Rick Byers wrote: LGTM2 In addition to Yoav's comments I'll also add that it makes sense to me if WebKit and Gecko don't want this. They each have a lot more flexibility in how they avoid unload handlers, and WebKit already just doesn't fire them when they don't

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

2023-06-30 Thread 'Thomas Steiner' via blink-dev
Timeline updated in developer-facing comms: https://github.com/GoogleChrome/developer.chrome.com/pull/6725. On Mon, Jun 26, 2023 at 10:57 PM Ayu Ishii wrote: > Hi blink owners, > > With request from partners, we are planning to update the timeline to > enable deprecation trial from M117

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

2023-06-30 Thread Rick Byers
LGTM2 In addition to Yoav's comments I'll also add that it makes sense to me if WebKit and Gecko don't want this. They each have a lot more flexibility in how they avoid unload handlers, and WebKit already just doesn't fire them when they don't want to. Chromium's enterprise customer base means

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

2023-06-30 Thread Yoav Weiss
LGTM1 On Fri, Jun 30, 2023 at 9:27 AM 'Fergal Daly' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsfer...@chromium.org, kenjibah...@chromium.org > > Explainer > https://github.com/fergald/docs/blob/master/explainers/permissions-policy-unload.md > >

[blink-dev] Intent to Ship: Permissions-Policy: unload

2023-06-30 Thread 'Fergal Daly' via blink-dev
Contact emailsfer...@chromium.org, kenjibah...@chromium.org Explainer https://github.com/fergald/docs/blob/master/explainers/permissions-policy-unload.md Specificationhttps://github.com/whatwg/html/pull/7915 Design docs

Re: [blink-dev] Intent to Ship: RFC 7616 Digest auth: Support SHA-256, SHA-512-256 and user hashing

2023-06-30 Thread Yoav Weiss
On Fri, Jun 30, 2023 at 8:38 AM Adam Rice wrote: > While plumbing use counters from //net back into Blink would be > technically possible, it would be a lot of work and we'd need some > compelling user benefit to justify it. > Could we simply add UMA instead? > > In this case, just having a

Re: [blink-dev] Intent to Ship: RFC 7616 Digest auth: Support SHA-256, SHA-512-256 and user hashing

2023-06-30 Thread Adam Rice
While plumbing use counters from //net back into Blink would be technically possible, it would be a lot of work and we'd need some compelling user benefit to justify it. In this case, just having a kill switch seems sufficient. On Thu, 29 Jun 2023 at 16:26, Yoav Weiss wrote: > Thanks for