-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Support return value from content script executed by MV2 #1425
Comments
Already supported for both MV2 and MV3: https://wxt.dev/guide/essentials/scripting.html#execute-script-return-values ![]() There is the other issue you created, #1428, but MV2 content scripts do already return values. So I'm gonna mark this specific issue as completed. We can discuss MV2 support for |
I get empty {} instead of '123' |
You're not returning the value... - '123'
+ return '123' |
It's the same, gets |
@harmonyharmo can you share a reproduction so I don't have to create it from scratch? |
Feature Request
Support return value from content script executed by MV2
chrome.tabs.executeScript
Is your feature request related to a bug?
"N/A"
What are the alternatives?
Message passing, which has more overhead and harder to write.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: