Re: [blink-dev] Re: Request for Deprecation Trial: Deprecate TLS SHA-1 server signatures

Per the conversation on the previous thread, carefully rolling this out to measure breakage seems like the right path forward. Do you have a timeline along which you'd like to run this experiment? M115-M118? -mike On Thu, Jun 8, 2023 at 9:54 PM 'David Adrian' via blink-dev < blink-dev@chromium.o

[blink-dev] Ready for Developer Testing: Borderless mode

Contact emailslaur...@chromium.org Explainer https://github.com/WICG/manifest-incubations/blob/gh-pages/borderless-explainer.md Specification https://wicg.github.io/manifest-incubations/index.html#dfn-borderless Design docs https://github.com/WICG/manifest-incubations/blob/gh-pages/borderless-ex

Re: [blink-dev] Intent to Ship: Document picture-in-picture

Thanks Domenic for mentoring and vouching :) I took a very cursory look at the API shape and sent a small fix , thanks for reviewing that. The concerns on https://github.com/WebKit/standards-positions/issues/41 are device independence an

Re: [blink-dev] Intent to Experiment: EditContext API

Do you all have a timeline in mind for experimentation? On 6/12/23 7:00 PM, 'Daniel Clark' via blink-dev wrote: Contact emails sni...@microsoft.com , shih...@microsoft.com , bemat...@microsoft.com

Re: [blink-dev] Intent to Ship: Document picture-in-picture

In the future, we may be able to do something on Android that doesn't support input without any change to Android APIs. If we wanted input in the PiP window, it would require changes to Android itself. That said, we haven't seen any interest from web developers for an inputless document PiP on Andr

RE: [blink-dev] Intent to Experiment: EditContext API

Tentatively M116 - M120 for the trial. From: Mike Taylor Sent: Tuesday, June 13, 2023 9:24 AM To: Daniel Clark ; blink-dev@chromium.org Cc: Chris Harrelson ; Anupam Snigdha ; Alex Keng Subject: Re: [blink-dev] Intent to Experiment: EditContext API Do you all have a timeline in mind for experi

[blink-dev] Intent to Experiment: scheduler.yield()

Contact emailsshase...@chromium.org Explainer https://github.com/WICG/scheduling-apis/blob/main/explainers/yield-and-continuation.md SpecificationNone Summary Provides a method for yielding control to the browser, which can be used to break up long tasks. Awaiting the promise returned by schedu

Re: [blink-dev] Re: Request for Deprecation Trial: Deprecate TLS SHA-1 server signatures

We plan to start in M115. Four milestones seems a bit long---this breakage likely either be immediately evident or a no-op. I was thinking M115 and M116, but we'll defer to your judgement. On Tue, Jun 13, 2023 at 2:50 AM Mike West wrote: > Per the conversation on the previous thread, carefully r

Re: [blink-dev] Re: Request for Deprecation Trial: Deprecate TLS SHA-1 server signatures

LGTM to experiment from M115 to M116. Good luck! -mike On Tue 13. Jun 2023 at 20:31 David Adrian wrote: > We plan to start in M115. Four milestones seems a bit long---this breakage > likely either be immediately evident or a no-op. I was thinking M115 and > M116, but we'll defer to your judgem

[blink-dev] Intent to Implement and Ship: Remove Payment Request User Activation Requirement

Contact emailsnbur...@chromium.org, smcgr...@chromium.org, i...@chromium.org Specificationhttps://github.com/w3c/payment-request/pull/1009 Design docs https://docs.google.com/document/d/16DHqqPWe5oM6Rucnn6Y1llhJ-DoEeLtTWFldJFg4iqA/edit#heading=h.w5782xqp7ab4 Summary To help developers reduce fr

Re: [blink-dev] Intent to Experiment: scheduler.yield()

LGTM to experiment from 115 to 118 inclusive. On 6/13/23 1:53 PM, Scott Haseley wrote: Contact emails shase...@chromium.org Explainer https://github.com/WICG/scheduling-apis/blob/main/explainers/yield-and-continuation.md Specification None Summary Prov

Re: [blink-dev] Intent to Ship: Add value argument to URLSearchParams's has() and delete()

Hey everyone! Indeed the site doesn't load properly even if we use unmodified chromium as Phistuck suggested! so sorry for the confusion caused. I have updated my CL https://chromium-review.googlesource.com/c/chromium/src/+/4519040 to include both use counters and a runtime flag and am awaiting

[blink-dev] Intent to Ship: deliveryType (Resource Timing)

Contact emails jbro...@chromium.org Explainer https://gist.github.com/jeremyroman/43f8f290f1f404d3b7f6cb708601c7f0 Specification https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-deliverytype Summary Expose information about how a resource was delivered. For example, resou

RE: [blink-dev] Intent to Experiment: EditContext API

> Although in the template this is phrased as a yes/no question, can you say > more about the WPT coverage and limitations? We currently do not have tests in web-platform-tests. There are tests outside the external/wpt folder: third_party/blink/web_tests/editing/input/edit-context.html

[blink-dev] Intent to Prototype: Web Serial support for Bluetooth RFCOMM services

Contact emails mattreyno...@chromium.org, melhui...@chromium.org Explainer https://github.com/WICG/serial/blob/main/EXPLAINER_BLUETOOTH.md Specification In progress Summary Support Bluetooth RFCOMM services in the Web Serial API. The Bluetooth RFCOMM (Radio frequency communication) protocol

Re: [blink-dev] Intent to Experiment: scheduler.yield()

Exciting stuff!! > The signal inheritance bit [1], however, would need transpilation support to propagate the current signal across async (Promise) boundaries. I couldn't find where this [1] goes. I'm very interested in this general area, and questions like whether we propagate by default or not,

[blink-dev] Re: Intent to Experiment: EditContext API

As a Web developer, I'm very happy to see this. Thank you! I notice that it introduces new editing events, however. It would be amazing if we could first get the ordering of the existing set of edit/compose events to be interoperable. For example, the following issue has stalled, waiting on Bli

Re: [blink-dev] Intent to Experiment: EditContext API

On Wed, Jun 14, 2023 at 12:03 AM 'Daniel Clark' via blink-dev < blink-dev@chromium.org> wrote: > *> **Although in the template this is phrased as a yes/no question, can > you say more about the WPT coverage and limitations?* > > > > We currently do not have tests in web-platform-tests. > > There a

[blink-dev] Re: Intent to Ship: FedCM Improvements: LoginHint, UserInfo, and Context

LGTM1 On Friday, June 9, 2023 at 9:10:14 PM UTC+2 Nicolás Peña wrote: > Contact emails > > n...@chromium.org > > Explainers > > https://github.com/fedidcg/FedCM/issues/382 > > https://github.com/fedidcg/FedCM/issues/426 > > https://github.com/fedidcg/FedCM/issues/456 > > Specification > > https:/

Re: [blink-dev] Intent to Prototype and Ship: contain-intrinsic-size: auto none support

On Fri, Jun 9, 2023 at 10:19 PM 'Vladimir Levin' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsvmp...@chromium.org > > SpecificationNone > > Summary > > This feature extends the existing contain-intrinsic-size syntax: none | > | auto && to also include auto && none: none | | >

Re: [blink-dev] Intent to Ship: Document picture-in-picture

On Tue, Jun 13, 2023 at 7:25 PM 'Tommy Steimel' via blink-dev < blink-dev@chromium.org> wrote: > In the future, we may be able to do something on Android that doesn't > support input without any change to Android APIs. If we wanted input in the > PiP window, it would require changes to Android its

Re: [blink-dev] Intent to Ship: Document picture-in-picture

On Wed, Jun 14, 2023 at 8:17 AM Yoav Weiss wrote: > > > On Tue, Jun 13, 2023 at 7:25 PM 'Tommy Steimel' via blink-dev < > blink-dev@chromium.org> wrote: > >> In the future, we may be able to do something on Android that doesn't >> support input without any change to Android APIs. If we wanted inp