MV3 changes/decisions

[tea]

Hey friends,

I see a lot of complaints about MV3 migration issues/rants (I have a large list of my own) and I see lots of meeting minutes from back and forth with Google/FF/Apple etc, what is lacking is what is going to change (if any) and when.

We have major effort to attempt (emphasis on attempt) to migrate our extension and not jeopardize losing our clients. We have a deadline from Google to migrate, but there is no commitment on any changes that people have made really good cases against (RTCConnection, background pages, websockets, just to name a few of the top reported ones).

IMHO the deadline announced by Google is not the right forcing function for these changes. It is better to champion changing some of the extensions that exercise features that are being changed and workout the kinks in the MV3 SDK before force feeding it to the entire community.

If there is something Google is going to change, is there a place where I can see this commitment so we do not waste time and resources on something that will be changed?

@Simeon maybe you can help me?

Thank you

[Artem Harutyunyan]

I very much second this sentiment! A lot of people are (silently or not so much) scratching their heads and thinking what to do. 

Would love to see a consolidated response from the community. 

Artem

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/d45a5536-037b-43c4-a861-94e8b7ff630bn%40chromium.org.

--

—
Co-Founder and CTO bardeen.ai
Explore | @bardeenai | Slack 

[Simeon Vincent]

If there is something Google is going to change, is there a place where I can see this commitment so we do not waste time and resources on something that will be changed?

While this isn't exactly what you're asking for, in the near future I want to start drafting a "known issues" page to the MV3 documentation. I'm thinking of this as a resource that would call out notable bugs and unimplemented capabilities that we plan to address. 

Simeon - @dotproto

Chrome Extensions DevRel

[Ryan Guilbault]

this may not be the appropriate place to ask this, but I'll proceed anyway: given the looming deadlines for compliance and the acknowledgment that there are outstanding issues/design alterations that will likely be needed to support the breadth of extension varieties that exist -- would Google be amenable to pushing back the hard deadline for compliance? it seems like a lot of developers are spinning wheels trying to work around limitations that may not need to be worked around (eventually)...but without knowing when the fixes will be available, we don't know how to schedule resuming our migration efforts. I would accept exceptions, i.e. 'if your extension relies on feature X, Y or Z, you may continue to publish the v2 manifest; otherwise you are required to publish v3'. since the extensions are reviewed anyway, you will know if anybody is applying for the special exception invalidly.

[tea]

@Ryan this is exactly why I was asking this.

@Simeon cataloging the list is great to avoid people asking about same things. However, the community here is looking for an authoritative statement from Google that says, for example, we will allow web sockets/persistent connections for the following use cases. Or don't bother reworking this part of your code because we will alleviate this issue. This request for persistent threads has been open for over 2 years, which predates the hard deadline. Since the deadline came out anyway, it seems to me that Google has no plans of addressing this challenge and maybe others :( I can speak for my team, we are spending a ton of time and money trying to rework things and if we can/should stop that effort, it would be of great value.

Thank you