-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a MV3 native host example #548
Comments
Hi darbid. Thanks for asking. Did you look through the issues to see if this question had already been asked? A few of us have asked now and I've been waiting for clarity since @dotproto kindly offered to add them in December #528 #526 To be fair though, the mv3 docs overview gives a good explanation of what has changed and the major change is killing background workers in favour of service workers which is covered at https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/ I suspect Native Messaging is dead now or will be soon. I'm not surprised, from a security standpoint that sounds terrifying! |
Update: It seems like things are happening #542 |
Thank you. Looks like vrong read my issue and has also noted it yesterday in 542. So all good there. I otherwise am sorry to say I do not share your opinion. I am not sure MV3 is clearly explained. For example do they make it clear how, when and in what circumstances Chrome will kill your service worker? The material promises promises :-) but where are they indicated in the material or examples? Do you have any links on your suspicion? I was unaware that removing Native Messaging formed any part of the roadmap for V3. |
Looks like I misread the warning on https://developer.chrome.com/docs/apps/nativeMessaging/ which talks about Chrome Apps being dead soon. I guess the examples link (pointing to mv2 archived extensions) at https://developer.chrome.com/docs/extensions/mv3/messaging/#examples will be updated soon and we'll see a sample with MV3 + Native Messaging. Have you tried https://github.com/GoogleChrome/chrome-extensions-samples/tree/master/mv2-archive/api/nativeMessaging but just bumping the version to 3 in the manifest? It seems pretty bare bones and doesn't seem to use a background worker so that might work? |
From a newbie perspective. It's quite difficult to start learning about Chrome Extensions while every resource on the internet (besides the docs) is talking about MV2, which is understandable: MV3 was just introduced in early Jan. But yes, I was hoping to find a MV3 example in the Google Chrome Extensions Samples official repo to wrap my head around. If there's any MV3 example already, please, point it to me. Thanks! |
A bit off topic but I agree - it's frustrating not getting any answers on these queries but I assume there's a good reason for it. That said it's uplifting to see that work is being done on this stuff in the background. For example there is now a basic MV3 extension walkthrough. I tested it on my machine recently and it works :) https://developer.chrome.com/docs/extensions/mv3/getstarted/ |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
We just merged an MV3 sample here: https://github.com/GoogleChrome/chrome-extensions-samples/tree/main/api-samples/nativeMessaging Thanks for your patience everyone. |
With the arguably some of most controversial changes being made and they are now being pushed through in Jan 2021, why does not a single extension link work? Where is 1 V3 example? Most importantly where is a Native Host example with V3?
why not release some of your test extensions that you did for Native Host messaging and V3.
The text was updated successfully, but these errors were encountered: