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

Browser compatibility broken #2832

Closed
HT-7 opened this issue May 25, 2023 · 3 comments
Closed

Browser compatibility broken #2832

HT-7 opened this issue May 25, 2023 · 3 comments

Comments

@HT-7
Copy link

HT-7 commented May 25, 2023

Until a few weeks ago, Odysee was able to run on Firefox 52 ESR from 2017, a time before Mozilla scraped all XUL extensions with Firefox Quantum, and I was proud of Odysee for caring that much about backwards compatibility. Now, a blank page appears even on a browser released as recently as 2019, Google Chrome 73.

Now, one might ask "Hey! Why don't you just update your browser?"

I obviously use recent versions of web browsers most of the time since that is more secure and stable, however, people might be in situations where they are unable to update their browser, such as the Linux dependency hell, restrictions in a work environment, running an emergency Linux boot disc which has an older version of Firefox, and the necessity of features only older versions are equipped with, such as the ability to deactivate the highly annoying pull-to-refresh trap.

Indeed, pull-to-refresh is more of a trap than anything remotely helpful. Since 2019, Google enforces the pull-to-refresh gesture on the mobile Google Chrome. New versions of Chrome do not give users the option to deactivate the anti-feature that is pull-to-refresh, so users who wish to use Chrome without pull-to-refresh are forced into using an earlier version which allows deactivating the pull-to-refresh annoyance through chrome://flags.

Ideally, browser updates would only bring improvements and have no unexpected negative side effects.

The unfortunate reality is that updates can and frequetly do break stuff.

Therefore it would be beneficial to reinstate compatibility with earlier versions of web browsers. Many people would be silently thankful.

Please note as well that the mobile website of YouTube even works in Chrome version 43 from 2015, as I have tested out of curiosity.

@keikari
Copy link
Contributor

keikari commented May 26, 2023

Blank page can also happen in modern browsers, if it's happening for same reason few force reloads(Ctrl+f5) should fix it. (Different reason)

@HT-7
Copy link
Author

HT-7 commented Jul 10, 2023

It has actually been fixed! Odysee works again on browsers from 2019 and even 2017.

Thank you, Odysee Team.

Thank you for your amazing work in creating that pretty user interface. And thank you for your outstanding browser compatibility.

@HT-7 HT-7 closed this as completed Jul 10, 2023
@tzarebczan
Copy link
Contributor

Woohoo!

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

No branches or pull requests

3 participants