-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
Please note that GitHub no longer supports old versions of Firefox. We recommend upgrading to the latest Safari, Google Chrome, or Firefox. #789
Comments
GitHub is not supporting Waterfox . I could not even edit my first comment |
See this pull request, discussion has been happening there: #784 |
As a funny sidemark: my second browser I use from time to time to cross-check things is Qupzilla, which wasn't updated for ages (I don't remember any update ever). And you get no warning when using that. Smells like deliberate action. And my first thought (right or not) was: ah, the first effects from the MS overtake … It is quite deliberate, as all it needs to make it work again is changing the UserAgent string. So it's not that the site cannot work but that they don't want it to. 😠 |
What's your UA of Qupzilla? What's a UA of Fallon, and how does GitHub respond? |
I downloaded one of the User Agent addons , set it to Edge on windows . |
So it should basically appear as an outdated Safari. I get no warning with that. Though I must admit I didn't test what features might be blocked (didn't log in with it to start with). Page doesn't render correctly – and as the OP noted, I cannot switch branches with it. First thought the warning is only shown when logged in – but then, thinking of broken cache/cookies I had a.o. deleted all cookies in Waterfox (which must effectively have logged me out), and promply got the warning. Maybe the warning just got lost in rendering 🤣 But as the page source doesn't contain it either, I doubt that.
What is Fallon? Btw: the UA override (making it "60.0" instead of "56.2") works perfectly, all features are available again (as far as I've tested). Even with Firefox 55 (which I'm currently using; this machine will be migrated to Waterfox next week). |
Fyi still getting issues with github edit / preview buttons are not working. |
Cant even edit my own post ^^ |
@mikeloeven sure you correctly implemented the work-around (as the code change most likely hasn't yet been published)?
Done. Reload the Github page(s), and all should work fine. It does here. Including preview and edit. |
Sorry, that was a typo on my mobile phone. Falkonhttps://userbase.kde.org/Falkon On FreeBSD, for 3.0.0:
|
QupZilla is outdated, but I should not expect GitHub's alert to be comprehensive. The note focuses on the three supported browsers. Side noteRe: github/site-policy#15 (comment) the Supported Browsers document is no longer a Site Policy. |
Falkon is not available on my machine. Maybe after the next distupgrade. And yes, that have been my thoughts as well: there might be browsers missing from their list. Which makes it even more stupid to go by the UA if it's possible to check feature compatibility another way … But nevermind: Qupzilla doesn't even render the page correctly – but the UA trick does it fine for me in Waterfox. I can absolutely live with that 😄 |
Misrepresenting Waterfox as Edge may be troublesome in some domains. about:config?filter=general.useragent.override @Tsoccerguy3 is there a preference for |
Which Linux distro? |
Linux Mint 18.3 currently. Based on Ubuntu 16.04 and supported at least for another year (LTS), hence I didn't yet upgrade to Mint 19 (too many possible side effects in my setup 😉) |
Thanks,
I see eight editions of 18.3. Which one? |
I am surprised changing the user agent fixes the buttons. Is github intentionally sabotaging the page or is it that edge doesn't support the features the site is trying to use so it falls back to an older script? |
No. |
Cinnamon. But that shouldn't make a difference on what's available in the repos 😉 |
I'm speechless. Welcome to the new world of Github courtesy of Microsoft... LMAO! ~Ibuprophen |
@ibuprophen1 my thoughts (see the 4th comment here) 🤣 |
GMX.net (German e-mail provider) also stopped support for this browser. Of course, the fault is with these websites and not this browser but it is a bit annoying for the users of Waterfox. |
Regarding the Waterfox Android Mobile App, so far I had found that the following manual input within the about:config seems to be working (it's only been a few days and I haven't seen the top message bar return yet). Interger: Name: String: I just wanted to provide my input to, hopefully help out. ~Ibuprophen |
GitHub now whitelists Waterfox based on the contents of its UA. @Tsoccerguy3 would you like to close this issue? |
Here is the plugin I'm using on Waterfox , It has its uses . easy to turn it on and off |
@Tsoccerguy3 can we close the issue? |
@Tsoccerguy3 If you started an issue, there's a close issue button next to the comment button. |
yes I see that Github has fixed issue |
Please note that GitHub no longer supports old versions of Firefox.
We recommend upgrading to the latest Safari, Google Chrome, or Firefox.
WaterFox 56.2.5 (64-bit} is not 100 percent compliant with GitHub
Can not select Branch or upload pictures
The text was updated successfully, but these errors were encountered: