Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

On Tue, Apr 18, 2023 at 8:32 PM Kai Ninomiya wrote: > (sending from correct email address this time) > Due to the nature of this removal I've elected to send this as an Intent > to Ship because we are seeking LGTMs. Please let me know if this is > inappropriate. > Contact emailskain...@chromium.o

Re: [blink-dev] Intent to Experiment: Explicit Compile Hints with Magic Comments

LGTM to experiment M114-M117 inclusive. Thanks for filing positions on this. While this doesn't pose any immediate interop risks, if other vendors can benefit from such magic comments, it'd be significantly better for web developers that we'd all converge on the same magic :) On Tue, Apr 18, 2023

Re: [blink-dev] Intent to Implement and Ship: Remove Secure Payment Confirmation user activation requirement

On Mon, Apr 17, 2023 at 9:42 PM Nick Burris wrote: > Contact emailsnbur...@chromium.org, smcgr...@chromium.org, > i...@chromium.org > > Specificationhttps://github.com/w3c/secure-payment-confirmation/pull/236 > > Design docs > https://docs.google.com/document/d/1DW4hGyuVzcN8sE8TC3YOkg6xO4XpUGZQNx

Re: [blink-dev] Intent to Extend Experiment: Privacy Sandbox Ads APIs

LGTM to extend experimentation M113-M115 (inclusive) On Fri, Apr 14, 2023 at 9:22 PM John Delaney wrote: > Hi Mike, > > Happy to give an update on each of these points: > > Each API is continuing to make progress on draft specs. All early > specifications have been published and each API is curr

Re: [blink-dev] Intent to Extend Origin Trial (3): Trial for SharedArrayBuffers in non-isolated pages on Desktop platforms

LGTM to extend the depreciation trial one last time till M121. Thanks for continuing to make progress on this hard problem. On Thu, Apr 13, 2023 at 2:45 PM Lutz Vahl wrote: > Contact emails > > v...@chromium.org cl...@chromium.org > > Explainer > > > https://docs.google.com/document/d/1zDlfvfTJ

Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

Given how close we are to M113 stable release, it may be too late for a merge back. If so, I imagine removal should be pretty low risk and easy but given all the trouble we've had lately I do think we need to follow the breaking change process, including putting the changes behind a flag

Re: [blink-dev] Intent to Ship: Scrollend Event

Thanks for the update and coordination with Mozilla David! Rick On Mon, Apr 17, 2023 at 12:09 PM David Awogbemila wrote: > A quick update here: > I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1827975 with mozilla > about the keyboard issue and they seem to agree on the behavior being >

Re: [blink-dev] Intent to Ship: Remove quirks mode behavior for option label attribute

Hey Joey, sorry for the delay. Yeah 0.01% puts this into the high risk range unfortunately. If you want to proceed, the next step would probably be to get a random sample of impacted URLs and evaluate the severity of breakage

Re: [blink-dev] Intent to Implement and Ship: Use RegExp v flag instead of u for HTML pattern attribute

Thanks for doing a thorough compat analysis of this Mathias. I can totally see this being one where all the examples we can find don't seem to cause breakage in practice. I know it's a lot, but if we looked at 40 random examples and found none of them to break, that would suggest an upper bound of

Re: [blink-dev] Intent to Prototype & Ship: Report Critical-CH caused restart in NavigationTiming

This makes a lot of sense to me. Normally we prefer to approve shipping only after spec PRs have landed, it looks like the PR is blocked on some work from you including landing the WPTs, right? I'd suggest you get this all landed under a status=experimental RuntimeEnabledFeature and see if we can g

Re: [blink-dev] Intent to Prototype & Ship: Report Critical-CH caused restart in NavigationTiming

That differs from my past experience (in which a proposed spec change is sufficient to move forward with a launch), but if you want me to build and test it all behind a flag before I get the go ahead here that's fine. ~ Ari Chivukula (Their/There/They're) On Wed, Apr 19, 2023 at 11:32 AM Rick By

Re: [blink-dev] Intent to Implement and Ship: Use RegExp v flag instead of u for HTML pattern attribute

Thanks for the guidance, Rick. I’ve prepared a CL moving the flag to status=experimental and I can commit to investigating 40 unique UseCounter hits and summarizing my findings. Fingers crossed the trend of “no actual breakage dete

Re: [blink-dev] Intent to Prototype & Ship: Report Critical-CH caused restart in NavigationTiming

Hi Ari, The documented process is to land features and specs before requesting approval to ship, as that gives the best possible chance for wide review and eventual interop. But we unfortunately often find ourselves in

Re: [blink-dev] Intent to Ship: Deprecate module size limit for WebAssembly.Module()

Hey Andreas, Do you know what the limits of other browsers are? If testing a 1 GB module is too slow to be reliable (sometimes timing out) then perhaps there's a large-ish module you can test with that still exceeds the current limits? Note that you could also add a manual test in WPT for the rea

Re: [blink-dev] Intent to Prototype & Ship: Report Critical-CH caused restart in NavigationTiming

Works for me, didn't realize that was the standard order. ~ Ari Chivukula (Their/There/They're) On Wed, Apr 19, 2023 at 11:58 AM Rick Byers wrote: > Hi Ari, > The documented process > > is > to land features and

Re: [blink-dev] Intent to Prototype & Ship: Report Critical-CH caused restart in NavigationTiming

Great, thanks Ari! No worries at all, checking to make sure the i's have been dotted and t's have been crossed is what the API owners are here for :-) On Wed, Apr 19, 2023 at 11:59 AM Ari Chivukula wrote: > Works for me, didn't realize that was the standard order. > > ~ Ari Chivukula (Their/Ther

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

Hi Abin (or Yoav?), What's blocking this spec PR from landing? As discussed here , our standard process is to do what we can to get spec changes fully landed if possible. Thanks, Rick On Wed, Apr 12, 2023 at 11:

Re: [blink-dev] Intent to Prototype & Ship: Expanded Wildcards in Permissions Policy Origins

Hi Ari, Given the discussion on your other intent , can you try to get spec PRs and WPTs landed for this before shipping this too? Thanks, Rick On Wed, Apr 12, 2023 at 12:06 PM Ari Chivukula wrote: > I don't h

Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

Apologies, I made an error in the I2S, this is in an attribute in GPUSupportedLimits (an interface), not GPUSupportedFeatures (a set). Hence considering it a breaking change. We have been considering a request to merge back to M113 but given we can't land on main without LGTM on an I2S, and we can

Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

Ah, good point :-) I just approved the CL for the purposes of attempting a merge to M113. Please follow up here on whether that happened or if we need to proceed with the breaking change for M114. Rick On Wed, Apr 19, 2023 at 12

Re: [blink-dev] Intent to Implement and Ship: Remove Secure Payment Confirmation user activation requirement

Le mercredi 19 avril 2023 à 03 h 45 min 37 s UTC-4, Yoav Weiss a écrit : On Mon, Apr 17, 2023 at 9:42 PM Nick Burris wrote: Contact emailsnbur...@chromium.org, smcgr...@chromium.org, i...@chromium.org Specificationhttps://github.com/w3c/secure-payment-confirmation/pull/236 Design docshttps:/

[blink-dev] Question about scroll restoring and missing docs

Hello, JS dev here. Was trying to understand what blink does in order to restore the scroll position on back navigation. I found "restoreScrollPositionAndViewState" here . Then tried to un

Re: [blink-dev] Intent to Implement and Ship: Use RegExp v flag instead of u for HTML pattern attribute

I wonder if we can get enough confidence with less work than investigating 40 randomly chosen sites from UseCounter hits. This is a population proportion problem, and https://sample-size.net/confidence-interval-proportion/ is a useful tool. If you check 40 cases and find no breakage (N=40, x=0) th

Re: [blink-dev] Intent to Ship: Removal of X-Requested-With in WebView

LGTM3 On Wed, Apr 12, 2023 at 1:14 AM Peter Birk Pakkenberg wrote: > Thank you Mike and Yoav, > > Can I get a third LGTM to let me proceed to a 1% roll-out on stable? > > > Sincerely, > [image: Google Logo] > Peter Birk Pakkenberg > Software Engineer > pb...@chromium.org > > > On Fri, 7 Apr 2023

Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

Thanks! Loko has filed https://crbug.com/1434745 for the merge request and I've filed https://crbug.com/1434766 as a releaseblock for 114 to track anything we need to do if it doesn't get merged back. I also fixed the GPUSupporteFeatures/Limits typos in the chromestatus page. -Kai (he/they) On

Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

Thanks! Loko has filed https://crbug.com/1434745 for the merge request and I've filed https://crbug.com/1434766 as a releaseblock for 114 to track anything we need to do if it doesn't get merged back. -Kai On Wednesday, April 19, 2023 at 10:08:53 AM UTC-7 Rick Byers wrote: > Ah, good point :-)

Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

Perfect, thank you! Good luck! On Wed, Apr 19, 2023 at 4:10 PM Kai Ninomiya wrote: > Thanks! Loko has filed https://crbug.com/1434745 for the merge request > and I've filed https://crbug.com/1434766 as a releaseblock for 114 to > track anything we need to do if it doesn't get merged back. > > I

Re: [blink-dev] Intent to Implement and Ship: Use RegExp v flag instead of u for HTML pattern attribute

On Wed, Apr 19, 2023 at 3:41 PM Philip Jägenstedt wrote: > I wonder if we can get enough confidence with less work than investigating > 40 randomly chosen sites from UseCounter hits. > > This is a population proportion problem, and > https://sample-size.net/confidence-interval-proportion/ is a us

Re: [blink-dev] Intent to Implement and Ship: Use RegExp v flag instead of u for HTML pattern attribute

I will say personally, as an author, I am generally accustomed to using special characters in my regex character classes freely, and hearing that the HTML spec is making a backwards incompatible breaking change that would prevent me from doing so is kind of surprising, and personally i would pr

Re: [blink-dev] Intent to remove: zoom CSS property

Hi Christoph, Thanks for the feedback. I left a omment inline below. On Tue, Apr 18, 2023 at 8:19 AM Christoph Nakazawa < christoph.po...@gmail.com> wrote: > Hey everyone, > > I currently depend on the `zoom` CSS property since using `scale` in > conjunction with perspective transforms results i

Re: [blink-dev] Intent to remove: zoom CSS property

On Mon, Apr 17, 2023 at 1:55 PM Morten Stenshorne wrote: > Chris Harrelson writes: > > > On Sun, Apr 16, 2023 at 11:45 PM Morten Stenshorne < > msten...@chromium.org> wrote: > > > > Chris Harrelson writes: > > > > > On Fri, Apr 14, 2023 at 5:09 PM PhistucK wrote: > > > > > > Any alternati

Re: [blink-dev] Fwd: Intent to Ship: Remove WebGPU limit maxFragmentCombinedOutputResources

As one last update for now, we've changed the CL to completely remove the feature. This way if we do succeed in merging to 113 the deprecated feature will not ship to stable, so the compat risk of removing it will be zero. Updating chromestatus. -Kai (he/they) On Wed, Apr 19, 2023 at 1:18 PM Ric

Re: [blink-dev] Intent to remove: zoom CSS property

Mike said: *"It would also be good to go through all duplicates and "See Also" bugs linked at https://bugzilla.mozilla.org/show_bug.cgi?id=390936 and see how we fare with a build that has zoom disabled."* Good idea. I checked all 37 of the site

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

On Wed, Apr 19, 2023 at 6:03 PM Rick Byers wrote: > Hi Abin (or Yoav?), > What's blocking this spec PR from landing? > Nothing is blocking AFAICT. Just a matter of someone with permissions clicking the button. > As discussed h