You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a summary of the consequences of migrating Negotiator from manifest v2 to v3.
With manifest v3, negotiator can no longer interactively modify web requests. Instead it has to use the declarativeNetRequest API to set up rules that the browser will apply.
These rules have some limitations compared what negotiator can do today.
The migration to V3 will be done once we're forced to migrate or earlier if we find the new branch to be good enough.
There might be a separate beta version published as a separate extension (since there's no beta testing built in chrome web store).
No wildcards in from domain
Thought not fully investigated, it looks like there is no wildcard support. Meaning only filters with exact domain or subdomain will be possible.
No dynamic user-agent
Negotiator will still be able to modify headers but only with static rules.
The feature to generate a new user agent on every request will no longer be possible.
One workaround would be for negotiator to frequently update the rules with a new user-agent every few seconds.
The text was updated successfully, but these errors were encountered:
This is a summary of the consequences of migrating Negotiator from manifest v2 to v3.
With manifest v3, negotiator can no longer interactively modify web requests. Instead it has to use the declarativeNetRequest API to set up rules that the browser will apply.
These rules have some limitations compared what negotiator can do today.
The migration to V3 will be done once we're forced to migrate or earlier if we find the new branch to be good enough.
There might be a separate beta version published as a separate extension (since there's no beta testing built in chrome web store).
No wildcards in from domain
Thought not fully investigated, it looks like there is no wildcard support. Meaning only filters with exact domain or subdomain will be possible.
No dynamic user-agent
Negotiator will still be able to modify headers but only with static rules.
The feature to generate a new user agent on every request will no longer be possible.
One workaround would be for negotiator to frequently update the rules with a new user-agent every few seconds.
The text was updated successfully, but these errors were encountered: