[blink-dev] Intent to Experiment: Long Animation Frame Timing

Contact emailsnrosent...@chromium.org Explainerhttps://github.com/w3c/longtasks/blob/main/loaf-explainer.md Specificationhttps://github.com/w3c/longtasks/blob/main/loaf-explainer.md Summary This is a extension of long tasks. It measures the task together with its subsequent rendering update, ad

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

I was targeting M116, which is aligned with what Firefox indicated. However, other browsers are yet to confirm their timeline, and they have indicated they might need more time, which makes 116 unrealistic if we want to get other browsers in addition to Firefox onboard. Regarding the outreach plan

Re: [blink-dev] Intent to Ship: CSS font-variant-position property

It's a shame to me to be holding back interop on the case of fonts having the superscript or subscript glyphs out of fear for the case where they don't. Perhaps we can treat the case of font-variant-position being used with fonts that lack the glyphs as a site bug that we can work to address indepe

Re: [blink-dev] Intent to Ship: CSS overlay property

Looking over the discussion that's happened over the past month it seems some confusion has been resolved and some improvements made to the spec. I don't see evidence of outstanding concrete points of disagreement. That, of course, doesn't mean others feel it's ready to ship (would be nice to see #

Re: [blink-dev] Intent to Ship: CSS font-variant-position property

I think it's worth noting that lack of interop here could take two different forms: (1) different behavior in different browser engines and (2) different behavior on different machines in the same browser engine, because of different system font availability. Some of the more advanced font capabil

Re: [blink-dev] Intent to Deprecate and Remove: “uuid-in-package” navigation with Web Bundles

LGTM2. -mike On Tue, May 23, 2023 at 12:38 PM Yoav Weiss wrote: > LGTM1 to remove, given the extremely low usage > > On Tue, May 16, 2023 at 3:50 AM Hayato Ito wrote: > >> Primary eng (and PM) emails >> >> hay...@chromium.org, ksakam...@chromium.org, denom...@chromium.org >> >> Summary >> >>

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

If refining the use counter is easy, that would be good to do, even if we don't block shipping on getting stable data for the use counter. But I think that careful local testing is the best way to get a sense for the risk on this. If you're confident you've hit the code path on the sites in questi

Re: [blink-dev] Intent to Ship : Content-type in Resource Timing

Thanks, LGTM3 On Mon, May 15, 2023 at 10:45 AM Yoav Weiss wrote: > > > On Mon, May 15, 2023 at 4:43 PM Mike Taylor > wrote: > >> I see that both the Resource Timing >> and Fetch >> PRs have landed - do

Re: [blink-dev] Intent to Deprecate and Remove: “uuid-in-package” navigation with Web Bundles

LGTM3 On 5/24/23 11:05 AM, Mike West wrote: LGTM2. -mike On Tue, May 23, 2023 at 12:38 PM Yoav Weiss wrote: LGTM1 to remove, given the extremely low usage On Tue, May 16, 2023 at 3:50 AM Hayato Ito wrote: Primary eng (and PM) emails hay...@chromium.org

Re: [blink-dev] Intent to Ship: CSS Motion Path

LGTM1 On Tue, May 16, 2023 at 9:03 AM Daniil Sakhapov wrote: > Issued the requests: > https://github.com/WebKit/standards-positions/issues/187 and > https://github.com/mozilla/standards-positions/issues/802. > > Also note: the spec has been largely finalised, so I don't expect any big > changes,

Re: [blink-dev] Intent to Ship: CSS Motion Path

LGTM2; looking forward to this launching. On Wednesday, May 24, 2023 at 8:55:07 AM UTC-7 Rick Byers wrote: > LGTM1 > > On Tue, May 16, 2023 at 9:03 AM Daniil Sakhapov > wrote: > >> Issued the requests: >> https://github.com/WebKit/standards-positions/issues/187 and >> https://github.com/mozil

Re: [blink-dev] Intent to Experiment: Long Animation Frame Timing

LGTM - excited to see people experiment with this! On Wed, May 24, 2023 at 3:06 AM Noam Rosenthal wrote: > Contact emailsnrosent...@chromium.org > > Explainerhttps://github.com/w3c/longtasks/blob/main/loaf-explainer.md > > Specificationhttps://github.com/w3c/longtasks/blob/main/loaf-explainer.md

Re: [blink-dev] Intent to Ship: CSS Motion Path

LGTM3 On Wed, May 24, 2023 at 5:55 PM Alex Russell wrote: > LGTM2; looking forward to this launching. > > On Wednesday, May 24, 2023 at 8:55:07 AM UTC-7 Rick Byers wrote: > >> LGTM1 >> >> On Tue, May 16, 2023 at 9:03 AM Daniil Sakhapov >> wrote: >> >>> Issued the requests: >>> https://github.co

Re: [blink-dev] Intent to Ship: CSS overlay property

I agree that https://github.com/w3c/csswg-drafts/issues/6429 which the TAG pointed to seems tangential to `overlay`. It's somewhat unfortunate, though, that we don't seem to have responded to their feedback in the month since they gave it. The conversation in https://github.com/w3c/csswg-drafts/is

[blink-dev] Layout changes

Hi I'm new to blink and I'm trying to capture the layout changes ( i.e. the changing x,y cordinates of an element) when there is a pure layout change caused by adding/removing of a node which in turn changes in the x,y coordinate of the element.I was trying to get these changes in void LayoutOb

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

Understood! I am going with the local testing approach for now, I think what I will do is raise exceptions if a difference in behavior is noted as Philip suggested, and see how many of these example sites raise them. This may take a little bit of time I think but trying my best! Thank You! On

[blink-dev] Intent to Ship: Non-composed Mouse and Pointer enter/leave events

Contact emailsmus...@chromium.org Specificationhttps://w3c.github.io/uievents/#event-type-mouseenter https://w3c.github.io/pointerevents/#attributes-and-default-actions Summary Make the event.composed property in mouseenter, mouseleave, pointerenter and pointerleave events "false" to be spec com

[blink-dev] Intent to Extend Experiment: Speculation Rules - Document rules, response header, deliveryType

Contact emails jbro...@chromium.org, adith...@chromium.org, isabo...@google.com, dome...@chromium.org, kenjibah...@chromium.org Explainer https://github.com/WICG/nav-speculation/blob/main/triggers.md https://github.com/w3c/resource-timing/issues/332 Specification https://wicg.github.io/nav-sp

[blink-dev] Intent to Ship: HTTPS Upgrades

Contact emailscth...@chromium.org, dadr...@google.com Explainerhttps://github.com/dadrian/https-upgrade/blob/main/explainer.md Specificationhttps://github.com/whatwg/fetch/pull/1655 Summary Automatically and optimistically upgrade all main-frame navigations to HTTPS, with fast fallback to HTTP.

Re: [blink-dev] Intent to Ship: HTTPS Upgrades

This is an awesome change that will make the web better! Did you run any experiments or origin trials to see how it works in the field? Are you planning on rolling it out slowly to see the impact? On Wed, May 24, 2023 at 4:13 PM Chris Thompson wrote: > Contact emailscth...@chromium.org, dadr...@

Re: [blink-dev] Intent to Ship: HTTPS Upgrades

We're planning to roll this out as a field trial, hopefully starting in Chrome 115 at 1% Stable in order to keep an eye impact. We've been testing our implementation in Chrome Canary/Dev/Beta channels for a while now to help test the feature and polish our implementation, which largely builds on Ch