BrowserWorks / Waterfox-Classic

The Waterfox Classic repository, for legacy systems and customisation.
https://classic.waterfox.net
Mozilla Public License 2.0
176 stars 33 forks source link

[Classic] Unsupported Browser to use Google Drive, Docs, Sheets, Sites, Slides, and Forms #5

Open Killogy opened 3 years ago

Killogy commented 3 years ago

I tried log in on Google Drive and now I get redirect to https://support.google.com/drive/answer/6283888?p=unsupported_browser

I tried changing User Agent but did not worked.

So this problem never will be fixed on Waterfox Classic ?

Edit: Ok It seems, using Modify Header Value addon fixed the problem.

Url: https://drive.google.com/* Domain and Sub: Checked Modify: Checked Header Value: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.9 Safari/537.36

Edit 2: It works even if Default Waterfox Classic User Agent is used but only if Modify or Deleted is checked.

hawkeye116477 commented 3 years ago

I can't reproduce that. Maybe try in safe mode.

Anyway, there are other Google things which are problematic, so I already submitted PR https://github.com/MrAlex94/Waterfox/pull/2185.

Killogy commented 3 years ago

It seems the problem was caused because I have another User-Agent for Google.com/search and avoid to show People also search for in the search results, so by deactivating this User-Agent fixed the problem, so Waterfox default User-Agent is not the culprit, itwas the User Agent I´m using for Google Search to avoid to show People also search for.

This was the culprit...

Url: https://www.google.com/search Domain and Sub: Checked Modify: Checked Url: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

So this Issue can be closed.

mkruselj commented 3 years ago

I have this issue too, without any user agent changes or whatnot. Unsure what's up. Latest WF Classic.

Killogy commented 3 years ago

Well, problem is happening to me again now. User-Agent do not fix it.

EDIT 1 : Weird, I have another Watefox profiles and I can to load Google Drive.

EDIT 2 : Also, I ´m logged in 3 Gmail accounts and only when one of my Gmaill accounts is used I can´t load Google Drive, if I load secundary account or another account then I can load Google Drive.

EDIT 3: Well, tested again, it seems my most used Gmail account get unsupported Browser error trying to load Google Drive, but not with others gmail accounts or other Waterfox profiles.

I deleted all cookies and nothing fixed this issue with one of my Gmail account.

Why this Unsupported Browser error is happening using only some Gmail account and not with others? using one profile and not with others Waterfox profiles?

Is happening on Waterfox G3 too, same gmail account.

With Edge Browser is working properly, I can load Google Drive.

Finally, using Modify Header Value addon and set User-Agent and Remove Checked allowed me to load Gmail Drive.

hawkeye116477 commented 3 years ago

Why this Unsupported Browser error is happening using only some Gmail account and not with others?

I guess that probably they chose some of your account for testing of new version of website. Addons like user-agent changer can also cause problems.

Anyway, WaterfoxCo/Waterfox#2185 will change default user-agent string and few site specific (incl. Google), so maybe that addons won't be needed that much.

mkruselj commented 3 years ago

Finally, using Modify Header Value addon and set User-Agent and Remove Checked allowed me to load Gmail Drive.

How exactly do you have MHV set up and which user agent?

Killogy commented 3 years ago

Finally, using Modify Header Value addon and set User-Agent and Remove Checked allowed me to load Gmail Drive.

How exactly do you have MHV set up and which user agent?

Url: https://drive.google.com/* Domain and Sub or only Domain: Checked Header Name: User-Agent Remove or Modify: Checked Url: Opera/31.0 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/31.0

P.S: As URL I need to use Opera/31.0 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/31.0 to load completly Google Drive content and broswing my drive. So this rule it works.

Url: https://drive.google.com/* Domain: Checked Header Name: User-Agent Add: Checked Url: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.9 Safari/537.36

mkruselj commented 3 years ago

Thanks! That worked.

Wasmachineman-NL commented 3 years ago

Speaking of Google, for some reason Translate is extremely broken under Classic 2021.07: https://i.imgur.com/dsZnwRr.png

Should I open a BR for this?

Wasmachineman-NL commented 3 years ago

That, and the three dots in GitHub also don't work so I can't edit the above post: https://i.imgur.com/xL0xoz5.png

hawkeye116477 commented 3 years ago

Google Translate is working fine. Maybe try safe mode.

For GitHub problem just use search feature, solution was mentioned some time ago.

Wasmachineman-NL commented 3 years ago

@hawkeye116477 Already tried safe mode, same issue.

hawkeye116477 commented 3 years ago

Ok, I see now the problem, translation is little different in Firefox.

However there is no JavaScript error on console and same problem is on Basilisk and Waterfox G3, so I have no idea what the problem exactly is.

There are only css errors, but same translation is in inspector, so it's rather not that problem.

Update: Waterfox G3 is based on Gecko 78.12. However Google Translate works fine on Firefox 78.12, so seems that maybe rather toggling some „privacy” options in about:config caused that.

Update 2: It's weird, but removing Waterfox part from user-agent fixes Google Translate... In case of Classic user-agent without Waterfox isn't sufficient, you need to refresh page and sometimes it works correctly. Anyway, in network requests I found suspicious URL https://translate.google.com/_/TranslateWebserverUi/jserror?script=https%3A%2F%2Ftranslate.google.comTranslateWebserverUi%2Fbrowserinfo&line=Not%20available.

However I'd recommend maybe just trying Bing Translator, cuz Google always wants to make it working mainly only in Chrome.

Update 3: I checked how it's on Firefox Nightly and there is also similar problem, sometimes it works fine, but sometimes it's bad.