Skip to content
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

[Classic] Update user-agent overrides #2185

Merged
merged 6 commits into from
Aug 2, 2021

Conversation

hawkeye116477
Copy link
Contributor

@hawkeye116477 hawkeye116477 commented Jul 26, 2021

More and more websites are closing the doors for Classic with message like „Please update your browser", so I think that the best would be to do same like Moonchild did, so set 68.0 user-agent.

To make it more comfortable for the future to change compatibility version I borrowed code from Moonchild.
Now UA compatibility version can be read from pref (general.useragent.compatMode.version). There is also possibility to toggle short/long Waterfox version string in user-agent (Waterfox 56.5.2021.07 or Waterfox 2021.07).

Default user-agent string looks like this: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Waterfox/56.5.2021.07.

I also updated site specific user-agents (some have been removed, few changed, few added, borrowed from Pale Moon and Basilisk).

wolfbeast and others added 5 commits July 25, 2021 15:31
In case of a missing pref, a hard-coded value is still used from the ctor.
To respond dynamically to the pref change, the mAppVersion string needs
to be rebuilt.
Includes some minor improvements for corner cases and removes leftover
b2g junk.
* Waterfox doesn't use separate name and version for engine
* Change version
* Allow to choose long or short version string
…ides

More and more websites are closing the doors, so it's time to do that.
@Felipefpl
Copy link

1st of all thank you for this change but there is something that came to my mind:

Firefox now is at version 90 and somewhat close to 91, how long will this last till version 68 is considered outdated by those same sites?

@hawkeye116477
Copy link
Contributor Author

Well, 68 is well-tested by Moonchild, it's definitely better than 56.

In the future maybe when more things will be ported, then maybe another bump would be good.

@Felipefpl
Copy link

Got it, thank you for the explanation, i hope 68 will last at least for a little bit.

* Remove undefined variable and replace it with hardcoded Gecko version
* Move version display variable, so it can be reused on other places
@hawkeye116477
Copy link
Contributor Author

It's approved, but not merged. What's the reason?

@MrAlex94 MrAlex94 merged commit 35bf621 into BrowserWorks:classic Aug 2, 2021
@MrAlex94
Copy link
Collaborator

MrAlex94 commented Aug 2, 2021

It's approved, but not merged. What's the reason?

I was traveling at the time, and lost Internet so could not approve until now :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants