-
Notifications
You must be signed in to change notification settings - Fork 372
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
Waterfox 56.2.3 (UA … rv:56.0; Waterfox) Gecko/20100101 Firefox/56.2.3) outdated according to the Outdated Browser service #294
Comments
Re: the closing comment in browser-update/browser-update issue 397 In lieu of experimental string 'A',
I'm now using an experimental string 'A-01',
|
…oesn't break websites (hopefully).
From the opening post:
tl;drStrings for Waterfox are now distinct from strings for Firefox 👍 The three strings that are primarily associated with Waterfox 56.2.3 (released yesterday):
Please, are these suitable for whitelisting? |
@SuperOP535 I did recently read the FAQ (thanks) but didn't want to repeat myself, #296 (comment) asks:
|
Hi
Please be aware that Waterfox 56.2.0 (tagged in GitHub) is a recent release, not yet outdated.
Given what's below, I don't expect the Outdated Browser service to grant an exception.
Any advice that you might like to share will be gratefully appreciated.
Essentially
For Waterfox 56.2.0, https://udger.com/resources/online-parser reports, in my (edge) case:
Mozilla/5.0 (X11; FreeBSD amd64; rv:56.0) Gecko/20100101 Firefox/56.0
– no hint that it's anything other than an outdated Mozilla Firefox.
Background
A few brief points.
Recent months
#178
· MrAlex94/Waterfox I began experimenting with string A below.Looking ahead
From The Waterfox Blog | Waterfox, Its Legacy and Looking to the Future (2018-04-28):
Some of the technical flesh to that bone is, if you like, at BrowserWorks/Waterfox#267 (comment) (2018-03-27) under Waterfox Quantum? · Issue
#267
· MrAlex94/WaterfoxExperimental string A
Mozilla/5.0 (X11; FreeBSD amd64; rv:56.2.0) Gecko/20100101 Firefox/56.2.0
Truly there will never be a Firefox 56.2.0.
The distinction might allow services such as http://outdatedbrowser.com/ and Browser-Update.org to be enhanced; maybe to associate
Firefox/56.2.0
with Waterfox (not with Firefox) and recognise Waterfox 56.2.0 as current.(Note to self: experiments with this string A lapsed when other things took priority. Resuming this morning.)
Experimental string B
Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Firefox/60.0
Of course that's not experimental where the browser is truly Firefox. However if I choose to use that string for Waterfox 56.2.0 – and this is not an invitation to others to follow suit, at this time – it'll be sane for me to treat it as experimental.
My own environment – edge case
That's exceptional, edge case, FreeBSD. The majority of Waterfox users use platforms that are Tier-1 for Mozilla Firefox support purposes.
The text was updated successfully, but these errors were encountered: