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
Have you tested that this is not an upstream issue or an issue with your configuration?
I have tried reproducing this issue in Chrome and it could not be reproduced there
I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description
using --user-agent in the command line doest work
How to Reproduce?
Right-click on the shortcut of the application (e.g., a browser) and select Properties.
Edit the Target Field:
In the Target field, append the --user-agent flag with the desired user agent.
Example for Google Chrome:
plaintext
Copy code
"C:\Program Files\Google\Chrome\Application\chrome.exe" --user-agent="YourCustomUserAgentString"
Apply Changes:
OS/Platform
Windows
Installed
https://ungoogled-software.github.io/ungoogled-chromium-binaries/
Version
131
Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dir
command line argument and it could not be reproduced thereDescription
using --user-agent in the command line doest work
How to Reproduce?
Right-click on the shortcut of the application (e.g., a browser) and select Properties.
Edit the Target Field:
In the Target field, append the --user-agent flag with the desired user agent.
Example for Google Chrome:
plaintext
Copy code
"C:\Program Files\Google\Chrome\Application\chrome.exe" --user-agent="YourCustomUserAgentString"
Apply Changes:
Click OK or Apply, then launch the shortcut.
Actual behaviour
checking the useragnet on https://www.whatismybrowser.com/ .
the user agnet doesnt change
Expected behaviour
the user agent supposued changed to the pass/used in the command line
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: