-
Notifications
You must be signed in to change notification settings - Fork 56
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
Clarify browser vendor positions on APIs in MV3 #146
Comments
We plan to implement the I'm not aware of any changes related to |
(also nit: keeping issues focused on one topic makes it easier to triage, discuss and eventually resolve) |
Ok, I think that's all we need for now to be honest. I just wanted to make sure it wasn't going away.
Totally fair! I can break things like this down slightly further in the future. Thanks for replying here. |
Notes from the 2022-01-20 meeting:
With that in mind I'm going to close this issue, since I mostly opened to have a link for the agenda. |
There are a few API's that I'd love to know each browser vendor's thoughts on:
Opening this issue with both so I can suggest these for the agenda.
The text was updated successfully, but these errors were encountered: