> degraded experience (or no extension at all). > badge, and our customers on the Beta channel using Chrome 112 will have a > For example, as it seems, in about five weeks we'll lose our Featured > very fast, especially considering the holidays. > since my mail in October, and the first deadline mentioned is approaching > Hey, apologies for the bumping of the thread, but we have no replies > On Wednesday, Novemat 5:39:59 PM UTC+2 wrote: > If someone could give an official update it would be amazing! (coffee on Let me know if one of the questions was unclear. I'd appreciate if someone could provide more information and clarity on the above. Can we show a custom message to users impacted? What does this mean in practice? Will the user experience on an MV2 extension be degraded, or the extension won’t start at all? Will it even be visible in the extensions menu? On the Chrome 112 experiments turning off MV2 support starting in January 2023 once having an MV3-compatible extension published? Will we get back our current Featured badge, rating, reviews, etc. Can we push an MV3 update and once approved, keep / get back our current users? Can we still push MV2 updates to existing users? What does this mean in practice? How does this effect current users? Forced uninstall? ![]() On the removal of MV2 extensions in January 2024 Will we get the Public status immediately and automatically again once we publish an MV3-compatible extension? Can we still publish MV2 updates to our users? Are other properties (rating, reviews, etc) remain the same after being Unlisted and then getting Listed again? What does this affect besides users not finding us via search and other similar methods? ![]() ![]() On making MV2 extensions Unlisted in June 2023 Will the extension that had the badge before automatically get it back once being MV3 compliant? Does this affect in any way how updates to the MV2 extension are approved and rolled out?
0 Comments
Leave a Reply. |