Hacker News Reader

Comment by lapcat | Hacker News Reader

The postponement was practically inevitable. Manifest v3 is a slow moving train wreck. Extension developers know it isn't ready and won't be ready by January.

Happy holidays to me, I can kick this can down the road too.

Look at some of the known issues: https://developer.chrome.com/docs/extensions/mv3/known-issue...

Userscript managers support

Estimated timeline: Canary support around October, 2022.

Service workers are not started in response to webRequest events

Estimated timeline: Targeting Canary support before October, 2022.

No way they were going to be ready to disable v2 in January for the stable channel.

View on HN

Deadline is still January if you want the featured badge or if you want to work in all the channels of Chrome. Seems like for most developers the deadline is the same.

Does having the Featured badge actually change anything meaningfully for your extension?

I think its more about not having customers ask why we don't have the badge. We primarily have business users so trust is super important.

Are you listed on the store? My company’s is unlisted and just part of the onboarding documentation. I think in my case nobody would give two craps about the badge.

What is "all the channels of Chrome"? What channels are there?

https://support.google.com/chrome/a/answer/9027636

"Chrome browser provides 5 channels: Stable, Extended stable, Beta, Dev, and Canary."

They mean nightly and beta builds.

very easily googleable - https://support.google.com/chrome/a/answer/9027636?hl=en

Thanks for the dv punishment check, @Barkingcat. You could've done a drive-by downvote, but you at least also left a comment, which I appreciate.

I was about to hop in the car and didn't have time to Google it, and pre-cognitvely figured others might also like to know without needing to also actively search it 100x, collectively.

Looking at my comment history, it's clear I frequently do research things myself and post a thorough comment in an effort to educate as well as inform others about terminology in HN discussions.

Please strive to be generous in your interpretations of others.

Please strive to be generous in your interpretation of my comment as well - likewise.

There are 3 posters including me replying to your question re what channels are, 2 including the same link. Hopefully that answers your question! (and by that I mean that I hope you didn't interpret that to be me sending you to a mistaken answer? if that's what you were refering to?)

That link is indeed genuinely from google.

I did downvote, but people also downvoted my comment as well, so I don't treat downvotes or upvotes as that important, sorry if that made you feel any other way.

The important thing is : did you get the answer to your question?

I sure did, within the first few minutes of asking! Thank you kindly, and take good care of Barkingcat.

Sounds similar to when Google said:

As a news website you don't NEED to use AMP. You'll just never appear in Google's news carousel, and won't be at the top of the news search results anymore. Sorry :(

Way too risky for devs to ignore the deadline and possibly get de-ranked from store search results.

More importantly deadline is still January 2023: "Chrome Web Store stops accepting updates to existing Manifest V2 extensions"

I think this has to change and may just be an outdated part of the timeline that hasn't been updated yet. After all, this item is still on the timeline too: "Enterprise policy can let Manifest V2 extensions run on Chrome deployments within an organization." But that doesn't make any sense anymore, because V2 will no longer be disabled on the stable channel in January, so there's not even a need for an enterprise policy to keep V2 extensions running.

It wouldn't make any sense to let V2 extensions keep running until June but disallow updates. What about security issues? They have to allow security updates.

That was always the plan no? They would stop allowing updates before they officially removed the extensions from the store...

No, see the announcement from a year ago. https://developer.chrome.com/blog/mv2-transition/

> There are two key dates for the phase-out:

> January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store. Developers may still push updates to existing Manifest V2 extensions, but no new Manifest V2 items may be submitted.

> January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions.

So V2 would be disabled in the stable channel simultaneously with the end of updates, in January 2023.

Only a special enterprise policy could keep V2 extensions running for a while after that time.

Yep, they just updated when Chrome Web Store stops accepting MV2 updates to January 2024: https://github.com/GoogleChrome/developer.chrome.com/pull/38...

Nice find!

The timeline has now been updated too: https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/

This was a mistake and has been corrected.

Reply on news.ycombinator.com