-
Notifications
You must be signed in to change notification settings - Fork 32
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 Classic] Problem with Google Support YouTube pages ? #77
Comments
It could be related to the errors logged in the Web Console.
https://web.archive.org/web/ + https://support.google.com/youtube/thread/119439627/how-do-i-change-my-youtube-layout-in-google-chrome-back-to-normal?hl=en |
So, it' an error from the site which serve its content in a wrong way for Waterfox But, yes... |
I apologize for the delay in answering your questions. I was thinking about some different ways to get around this and have a lot of other tasks to do.
In case of Intl.RelativeTimeFormat() constructor as part of the ECMAScript Internationalization API, this seems to be not supported before Firefox 65 as described on web pages:
It is worth a mention that I also get the same result and even more logged web console error messages with the Pale Moon 31 web browser.
I dont't know exacly what you mean. However, the following configuration is preferred by me for the time being to work around the issue with all Google support threads. This NoScript Classic Firefox extension Script Surrogate creates a surrogate for the missing JavaScript object before the HTML parsing starts:
|
Yep, that's work fine! Now i need to manage an other addon, hmmmm. |
Test link:
[Google Support YouTube.](https://support.google.com/youtube/thread/119439627/how-do-i-change-my-youtube-layout-in-google-chrome-back-to-normal?hl=en)](https://support.google.com/youtube/thread/119439627/how-do-i-change-my-youtube-layout-in-google-chrome-back-to-normal?hl=en)
I have tested with Waterfox Classic v.56.6 (last update):
But always not see the text in the page.
No problem with:
What's the problem?
Can you fix it or explain a workaround?
And as usual: Thanks for your work!
The text was updated successfully, but these errors were encountered: