Re: [blink-dev] Web-Facing Change PSA: NotRestoredReasons name change

I would like to rollout this change in M135 (cutting next week). There has been no response to Domenic's argument that this is *very unlikely* to cause breakage. Unless someone argues that this needs to be more than a PSA, I will proceed, Fergal On Wednesday, November 13, 2024 at 6:11:08 PM UT

Re: [blink-dev] Web-Facing Change PSA: NotRestoredReasons name change

I spent some time discussing this with the team internally before this was sent, with the tentative conclusion that a PSA was appropriate instead of a full Intent to Ship. Here are the factors that indicate this to me: - As Yuzu states, in practice we expect these values to be treated as op

Re: [blink-dev] Web-Facing Change PSA: NotRestoredReasons name change

+bfcache-...@chromium.org On Thu, Nov 7, 2024 at 3:01 PM Yuzu Saijo wrote: > Thanks Yoav for the question. > > I realized that we have a usage counter but in a wrong place >

Re: [blink-dev] Web-Facing Change PSA: NotRestoredReasons name change

Thanks Yoav for the question. I realized that we have a usage counter but in a wrong place

Re: [blink-dev] Web-Facing Change PSA: NotRestoredReasons name change

What does current usage look like? Have you reached out to folks who may be using the API to notify them that they'd need to adapt their backend code? On Tue, Nov 5, 2024 at 5:57 AM Yuzu Saijo wrote: > > We are going to change the names reported in NotRestoredReasons API so > that they match the