Pausing Manifest V2 phase-out changes

Re:Pausing Manifest V2 phase-out changes by runlevel1 on Friday December 09, 2022 @09:32PM (#33929202)

I just wrote a quick script to survey extensions featured on the Chrome Web Store.

Of the 1200 checked so far:

Manifest v2: 872

Manifest v3: 328

They'd basically be breaking almost 2/3 of extensions.

EDIT: Just noticed 9 out of 12 of Google's own extensions are still on manifest v2 as well: https://chrome.google.com/webstore/category/collection/by_ch...

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by tech234a on Friday December 09, 2022 @11:27PM (#33929839)

Note that Google's collection doesn't seem to include all of their extensions. For example, they are missing Google Voice, Google Dictionary, Send from Gmail, Page Analytics, Google Tone, Chrome Web Store Launcher, RSS Subscription Extension, Google Scholar Button, IBA Opt-out, Google Mail Checker, Google Similar Pages, Endpoint Verification, Chrome Remote Desktop, Chromebook Recovery Utility, Certificate Enrollment for Chrome OS, Screen Reader, Print, Google Docs Offline, and I'm sure there are plenty of other Google extensions that I missed in my search. Some of them have been abandoned for a number of years.

Also, this site [1] has been tracking Manifest V3 migration, but I think they might be incorrectly including Apps and Themes in their counts (I believe the 180K figure represents all of the items on the store [2]) which might be throwing off the numbers a bit.

[1]: https://chrome-stats.com/manifest-v3-migration

[2]: https://www.debugbear.com/blog/counting-chrome-extensions

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by akiselev on Saturday December 10, 2022 @03:07AM (#33930894)

Back in my day attaching Google’s name to a product was a positive development. Remember GMail?

“Unmitigated shitshow” is the only thing that comes to mind today.

What tech giveth, tech taketh away.

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by szundi on Saturday December 10, 2022 @08:32AM (#33932467)

This is so true. They even closed down their IoT core for pennies.

Google = unreliable as business partners and more shitty every day anyway.

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by ethbr0 on Saturday December 10, 2022 @09:36AM (#33932958)

It's almost like they have an incorrect corporate reward function, that their employees are then optimizing...

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by danaris on Saturday December 10, 2022 @12:34PM (#33934564)

> What tech giveth, tech taketh away.

Honestly, I would say it's more "what tech giveth, greed taketh away."

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by rasz on Saturday December 10, 2022 @11:34AM (#33933962)

Im afraid this statistic wont tell you the whole picture because there are things strictly prohibited/not supported by v3. 100% v3 will simply mean all the extensions using those APIs simply got deleted and no longer exist.

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by sounds on Saturday December 10, 2022 @11:42AM (#33934044)

Our solution has been to uninstall Chrome. Firefox, and when unavoidable, DuckDuckGo's private browser, are doing fine.

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by Spivak on Saturday December 10, 2022 @07:58PM (#33938807)

Firefox is gonna do MV3 too except keep the request intercepting API so it’s not terribly different.

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by mnoorenberghe on Sunday December 11, 2022 @08:57AM (#33943208)

Firefox and Safari are continuing to support HTML pages to run the background code in rather than forcing developers to use service workers with no DOM access.

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by lelandfe on Saturday December 10, 2022 @09:17AM (#33932798)

Isn't one of the requirements to be featured using Manifest v3?

https://developer.chrome.com/docs/webstore/best_practices/

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by tech234a on Saturday December 10, 2022 @04:20PM (#33936911)

I don't think the best practices are necessarily the requirements for the featured badge. Manifest V3 is not yet a requirement for being featured, for example look at the listing for uBlock Origin, which still uses Manifest V2.

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by lelandfe on Saturday December 10, 2022 @07:02PM (#33938421)

https://developer.chrome.com/docs/webstore/discovery/#featur...

> Chrome team members manually evaluate each extension before it receives the badge, paying special attention to the following:

> 1. Adherence to Chrome Web Store’s best practices

I guess it’s “evaluated” on adherence, rather than it being a hard requirement

[ Parent | on HN ]

Re:Pausing Manifest V2 phase-out changes by ehsankia on Saturday December 10, 2022 @04:10AM (#33931182)

Eh, before the post in OP, I believe the timeline was June 2023 MV2 extensions go unlisted and January 2024 they get deleted. People do procrastinate but we're still far from 2/3 being "broken".

[ Parent | on HN ]