CarbonPepper Posted December 22, 2014 Report Share Posted December 22, 2014 Maxthon Version 1.0.5.3 for linux. All google web services report in a yellow bar: "This version of Chrome is no longer supported. Please upgrade to a supported browser. Dismiss" On gmail, google drive etc. Screenshot: I'm aware of a workaround by tweaking the useragent, but a proper solution would be better. (There was another thread with this problem but it was marked as solved too early and without a solution). Link to comment Share on other sites More sharing options...
7twenty Posted December 22, 2014 Report Share Posted December 22, 2014 Tweaking of the UA might be your only option, but it's also dependent on how they're detecting the browser version. It might be a case of just having to wait till MX for Linux is updated. What's the standard UA for MX for Linux? http://whatsmyuseragent.com/ Link to comment Share on other sites More sharing options...
30947894 Posted December 22, 2014 Report Share Posted December 22, 2014 Mozilla/5.0 Mozilla version 5.0 Originally indicated the Netscape web browser, now a generic term which most modern browsers use X11 X11 Linux x86_64 Linux version x86_64 Linux Mint 17 Qiana Linux version Mint 17 Qiana AppleWebKit/537.36 AppleWebKit version 537.36 KHTML, like Gecko KHTML, like Gecko Chrome/33.0.1750.0 Maxthon/1.0.5.3 Safari/537.36 Chrome version 33.0.1750.0 Maxthon/1.0.5.3 Safari/537.36 Link to comment Share on other sites More sharing options...
7twenty Posted December 22, 2014 Report Share Posted December 22, 2014 Works fine for me using the standard UA for the WinPC version and also if changed to the Linux UA as noted above. So seems to me they're using another form of detection, which would make more sense. On the other hand if the UA change does work for you I can't see any reason why you shouldn't use it. If anything it should make the browser more compatible across sites leading to less issues like this. Link to comment Share on other sites More sharing options...
CarbonPepper Posted January 20, 2015 Author Report Share Posted January 20, 2015 I'm a big believer in fixing things at source "if the UA change does work for you I can't see any reason why you shouldn't use it" How about, if the UA change does work, I can't see any reason they can't build it into the maxthon code. I hate workarounds. I love solutions Link to comment Share on other sites More sharing options...
CarbonPepper Posted January 20, 2015 Author Report Share Posted January 20, 2015 Update: I've since discovered this thread about linux development stalled: http://forum.maxthon.com/thread-13696-1-1.html Which I guess is why there've been suggestions of workarounds? If so I'm grateful for the workaround suggestions, but if there's little likelihood of a proper solution I'll find another browser Link to comment Share on other sites More sharing options...
7twenty Posted January 25, 2015 Report Share Posted January 25, 2015 CarbonPepper replied at 2015-1-20 23:43 I'm a big believer in fixing things at source "if the UA change does work for you I can't see an ... I'm sorry, but I still don't understand your hesitation to use the UA change as described assuming it works for you. Even if Maxthon did update the Linux version today, if they don't change the codebase to a higher version of Blink then the UA won't change as the whole purpose of the UA is to tell sites the general capabilities of the browser. As standard the browser should not be faking these details. But if you want to change/update them than that is a possibility. Link to comment Share on other sites More sharing options...
Recommended Posts