Re: [blink-dev] Request for Guidance

Hi Ajay, Every new web-exposed feature, even if it's a small addition to an existing API, needs an intent to ship. This helps us make sure that all new features are tracked and understood by the community, and have the right level of open standards engagement, consensus and so on. Also, it

[blink-dev] Re: Intent to Ship: Speculation Rules (Prefetch)

On Tue, Apr 19, 2022 at 6:54 AM Theodore Olsauskas-Warren wrote: > Hi Team, > > Have there been any changes since the conclusion of the previous > experiment? > There have been some bug fixes and tweaks on the margins, but the API surface hasn't changed substantially since the previous

Re: [blink-dev] Request for Guidance

I'm not an API owner, but since it's shipped already I would suggest you just do an Intent to Prototype & Ship. If it's a relatively small feature then hopefully it will also be relatively quick for API owners to review. On Thu, Apr 21, 2022 at 5:34 PM 'Ajay Rahatekar' via blink-dev <

[blink-dev] Request for Guidance

Hello blink-dev owners, The Chrome team is planning on implementing screen labels defined in the draft spec for Multi-Screen Window Placement . The tracking bug for the implementation is here

[blink-dev] Deadline extended: There's still time to host at lightning talk at BlinkOn 16

Bcc: blink-dev@ and BlinkOn 16 attendees TLDR: The deadline to host a lightning talk at BlinkOn 16 in 1H 2022 has been extended - sign up here by Friday, April 22nd. Hi everyone, Good news

Re: [blink-dev] Re: Intent to Deprecate and Freeze: The User-Agent string

Hey all! Looks like I'm jumping on this train a little bit late, but still probably I’m not the last person on earth that is in the field of the web and only recently stumbled this change. After reading all this thread carefully I still feel that not everything was resolved so I’m posting

[blink-dev] Re: Intent to Ship: Local Fonts Access API

On Wed, Apr 20, 2022 at 4:21 AM Yoav Weiss wrote: > > > On Wed, Apr 13, 2022 at 6:46 PM Joshua Bell wrote: > >> On Wed, Apr 13, 2022 at 6:36 AM Yoav Weiss >> wrote: >> >>> Also, any learnings/feedback from the Origin Trial? >>> >>> >> Not distinct from the dev trial (i.e. developers trying the

[blink-dev] Intent to Implement and Ship: Fullscreen Capability Delegation

Contact emails mus...@chromium.org, m...@chromium.org Explainer https://github.com/WICG/capability-delegation Specification https://wicg.github.io/capability-delegation/spec.html (Work in progress for fullscreen algorithm change: https://github.com/WICG/capability-delegation/pull/28) Design

Re: [blink-dev] Intent to Deprecate and Remove: Battery Status API in Insecure Origins

Hi everyone, M103 is here, so I'd like to double-check if I can go ahead and stop exposing the Battery Status API to insecure origins as described below. The numbers in https://chromestatus.com/metrics/feature/timeline/popularity/2199 remain flat (as explained, the percentage is pretty high

Re: [blink-dev] Intent to Ship: Early Hints preload/preconnect during Navigation

Hi Yoav, On Thu, Apr 21, 2022 at 3:26 PM Yoav Weiss wrote: > > > On Thu, Apr 21, 2022 at 4:13 AM Kenichi Ishibashi > wrote: > >> Contact emails >> >> ba...@chromium.org, denom...@chromium.org >> >> Explainer >> >> https://github.com/bashi/early-hints-explainer/blob/main/explainer.md >> >>

Re: [blink-dev] Intent to Ship: Early Hints preload/preconnect during Navigation

On Thu, Apr 21, 2022 at 4:13 AM Kenichi Ishibashi wrote: > Contact emails > > ba...@chromium.org, denom...@chromium.org > > Explainer > > https://github.com/bashi/early-hints-explainer/blob/main/explainer.md > > Specification > > https://tools.ietf.org/html/rfc8297 > >