UserAgent-Switcher
UserAgent-Switcher copied to clipboard
ray-lothian
[Firefox] Whitelist mode doesn't work; custom user-agent is still applied on some sites
With the extension set to "white-list mode", custom user-agent should only be applied to the sites listed in the white-list. I have that list set to foobar.doesnotexist.com, so the custom user-agent should never be applied. However, when navigating to meet.google.com, the extension icon is orange, indicating that custom user-agent is applied. This doesn't happen when navigating to other sites such as github.com, where the extension icon is orange-blue, indicating that the site is ignored.
Why does this occur, and what makes meet.google.com somehow special in how this extension handles it?
Changing to implement the whitelist via "custom mode", where you list each whitelisted website in the JSON object and map it to a user-agent string in the extension settings, rather than setting the custom user-agent through the addon tooltip, does not have the same issue, and custom user-agent is enabled/disabled as expected on all websites.
Changing to implement the whitelist via "custom mode", where you list each whitelisted website in the JSON object and map it to a user-agent string in the extension settings, rather than setting the custom user-agent through the addon tooltip, does not have the same issue, and custom user-agent is enabled/disabled as expected on all websites.
I had the same issue. Thank you for your solution. This worked for me in firefox, but I had to clear cookies for websites listed in JSON object.
This seems to be resolved, and maybe fixed in v3 if there is an issue.
@ray-lothian if you need assistance triaging these and PRs let me know.
This seems to be resolved, and maybe fixed in v3 if there is an issue.
I'm confused about the status of this project - there are 0.6.x tags from last year, but the version I have installed is 0.5.0 from AMO, which is from 2023 and is the latest version they have. Has the issue been fixed since then? Does someone need to add a new release on AMO?
This seems to be resolved, and maybe fixed in v3 if there is an issue.
I'm confused about the status of this project - there are 0.6.x tags from last year, but the version I have installed is 0.5.0 from AMO, which is from 2023 and is the latest version they have. Has the issue been fixed since then? Does someone need to add a new release on AMO?
The new version should be uploading to AMO, according to #222 but that was a couple of days ago. I am not certain on how long it takes for updates to push to AMO, so it could just be waiting on Mozilla?
This seems to be resolved, and maybe fixed in v3 if there is an issue.
I'm confused about the status of this project - there are 0.6.x tags from last year, but the version I have installed is 0.5.0 from AMO, which is from 2023 and is the latest version they have. Has the issue been fixed since then? Does someone need to add a new release on AMO?
The new version should be uploading to AMO, according to #222 but that was a couple of days ago. I am not certain on how long it takes for updates to push to AMO, so it could just be waiting on Mozilla?
It's been another 9 days since your comment, I think AMO review generally doesn't take this long? Was the update ever actually pushed to AMO?
It was submitted and got rejected after 7 days. A fix has been submitted.
