Google no longer serving up Firefox 2 compatible search



  • Gmail is acting up again in Opera 10.10. It logged me out, and when I try to log in, it fails, instead displaying some (probably erroneous) page saying it won't let me log in because my browser is "insecure". Yet it lets me log in with Firefox 2.
  • I pretty much gave up on older browsers and modern email. Instead I installed some oddball tweaks and got Outlook 2003 to work with MS hotmail. I think at one point I got gmail working.
  • Does changing the user agent to Opera 12.x work? It won't serve the 'new' GMail but it should serve the older version.
  • Opera 10.10 does not seem to permit changing the user agent to any arbitrary value, although it has options for "Mask as Firefox" and "Mask as IE".
  • edited July 30
    In spite of YouTube's Classic deprecation, the page that appears when you are given a choice of accounts to use is still based on Classic with no Polymer equivalent existing.

    And that page is broken as it always signs you into one particular account regardless of the one you choose. At least on UXP (Pale Moon)-based browsers.
  • Does a newer browser help? I know Pale Moon has a different UX, but from what I heard it is still based on Firefox 52.

    But why bother with it when there is nothing worth watching?
  • I'm with Firefox 68 ESR currently, and I'd think whenever my browser gets upgraded to 78 ESR in about two months, the experience with the new YouTube might be better, but I'm just assuming things.
  • ESR versions usually are a bit behind shortly before they are EOL.
  • I'm only with ESR because I began to hate the regular Firefox over time, even with higher memory usage I've been seeing. Plus, Firefox 55 would've been the last straw for me.
  • I'm still pretty content with Pale Moon. Though some times anything Google quits on it.I can't stand modern firefox. The last good one (to me) was 28 before they just started copying other browsers.

    Pretty much suits my needs perfectly. And not resource hogging either.
  • edited September 11
    Just happened notice - the main login page on does not work in the latest Palemoon, newmoon, Basilisk for XP, and TenFourFox. Clicking the "sign in" button just does nothing.

    Seems extra dick-headed on a job site like Monster. Yea, everyone can buy a new Windows 10 laptop running Gurgle Crumb... as soon as they get a job... but they can't because they can't access the site! Might as well just round up everyone without the latest and greatest and literally exterminate them.
  • edited September 11
    Hmm, it works on Pale Moon with my gutted 10240 install.

    But something is telling me there might be some useragent sniffing shenaniganry where it blocks out old OS.

    That inefficient page optimization is killing me. Probably another Google SSO implementation that looks horrible on anything other than a phone. And especially horrible on a high-res not-so-shortscreen monitor.
  • It seems to work on Firefox 68 for me. It is somewhat new but already a year old.
  • Hmm. The palemoon version I tested is 28.13.0 32-bit on Windows 10 32-bit. It does work in current official Firefox 32-bit. I did try disabling the ad blocker just to be sure.

    BTW, one does not need an account to see if the button does not work. Enter anything that looks like an e-mail address, and a gibberish password, and clicking the button won't even display an error.
  • edited September 13
    Ah, the sign in button you have to click. I simply thought getting to the page was the issue, my bad.

    Specifically, this code:
    function loginFormValidate() { resetLoginFormValidationMessage(); var isEmailFieldValid = validateEmailField(); var isPasswordFieldValid = validatePasswordField(); if (isEmailFieldValid && isPasswordFieldValid) { login(event); return false; } }

    On proper browsers, the code doesn't execute because "event" isn't passed down correctly to login() from wherever it was declared initially, so the entire login button's code is invalidated and not run.
    On other browsers (chrome), their JS engines don't care and assume. That is wrong. Another instance of web-developers catering to Chrome and following its quirks (just like IE6!!!!). Forcing conventional Firefox to adopt that and follow suit just to stay relevant.
    And leaving users of browsers that don't adopt such insanity in the dust.

    I actually looked this one up. I can see a few results from years ago where pulling this off would work fine in Chrome, but not on Firefox.
  • edited September 14
    Pale Moon being based on Firefox 38 from 2015 might explain why the JS engine acts differently.

    There is for such things, so I might see if it is already there.
  • It's a sad day... disable_polymer=1 has stopped working. We're all forced with the new YouTube from now on.

Sign In or Register to comment.