Any plans what will get into 1.4?

53 views
Skip to first unread message

Tomislav Zorčec

unread,
Dec 7, 2020, 1:05:36 AM12/7/20
to chrome-debugging-protocol
Hello,

  we would like to workaround some problems we will encounter because of the MV3. (removal of the blocking webRequests API)

For that we need "fetch", and we would like to confirm if you are planning to make it stable. Are there any changes you are planning to do related to MV3?

Sincerely, Tomislav

Andrey Kosyakov

unread,
Dec 7, 2020, 1:26:11 PM12/7/20
to Tomislav Zorčec, chrome-debugging-protocol
Hi Tomislav,

in general, we're only bumping the version when we break compatibility (i.e. remove non-experimental methods or arguments etc), so your question is technically not related to 1.4. In particular, Fetch domain is out of experimental as of m87. That said, we do not recommend using protocol methods as a substitute for extension APIs for regular extensions, primarily because of a higher level of privilege required to talk CDP to the browser and associated extension review process and browser-side UX.

Best regards,
Andrey.


--
You received this message because you are subscribed to the Google Groups "chrome-debugging-protocol" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-debugging-p...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chrome-debugging-protocol/ab349f70-8fdf-4a94-9e8c-940cff50408cn%40googlegroups.com.

Tomislav Zorčec

unread,
Dec 9, 2020, 3:31:39 AM12/9/20
to chrome-debugging-protocol
Perfect, thank you for the quick response and all the information.
We will keep your recommendation in mind.
Reply all
Reply to author
Forward
0 new messages