Recommended Posts

Hey, today i noticed that google loads in nightly the old-fashioned search in nightly. I tried with a new profile too. It doesn't happen in Aurora, nor in Chromium, nor in IE9.

Some screenshots:

err2.PNG

Also in the italian version the logo is loaded incorrectly:

err1.PNG

This things make me realize how bad looking the internet was in the past :)

Google often use cookies to set how the site should appear to you when they are testing stuff (for example if you get the new Google bar or not). In this case, it appears your Nightly has somehow got one to give you the old design, which must be some sort of error on Google's end. Nice to see though!

Google often use cookies to set how the site should appear to you when they are testing stuff (for example if you get the new Google bar or not). In this case, it appears your Nightly has somehow got one to give you the old design, which must be some sort of error on Google's end. Nice to see though!

I thought that too, but after deleting the cache and cookies nothing changed

I got the same problem in nightly but changing the user agent fixes it for me. In about:config add "general.useragent.override" and string value "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" or whatever previous version of firefox.

Websites sometimes appear differently on other browsers and they detect that by sniffing the user agent. Try using iPad safari browser user agent and you can emulate googles iPad layout on firefox.

Mozilla/5.0 (iPad; U; CPU OS 4_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8F190 Safari/6533.18.5

edit:

It appears that today's nightly changed user agent formatting. https://bugzilla.mozilla.org/show_bug.cgi?id=588909

old nightly: Mozilla/5.0 (Windows NT 6.1; rv:13.0a1) Gecko/20120217 Firefox/13.0a1

today's nightly: Mozilla/5.0 (Windows NT 6.1; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1

This broke the google. So temp workaround is to manually change user agent or wait for google to fix it on their end.

The probably used that part of the useragent to detect if the rendering engine is modern enough for the standard design otherwise it will revert back to the old for compatibility reasons. The changing of the date format broke this backwards compatibility (Better to use dates than version numbers it would be simpler to do when Nightlies are involved which won't have a predictable version number)

Hey, today i noticed that google loads in nightly the old-fashioned search in nightly. I tried with a new profile too. It doesn't happen in Aurora, nor in Chromium, nor in IE9.

Some screenshots:

err2.PNG

Also in the italian version the logo is loaded incorrectly:

err1.PNG

This things make me realize how bad looking the internet was in the past :)

How bad looking it was? What's bad about that? It's called simple and simplistic and it loaded very fast too, I bet, which is how I wish it still was instead of all the bloat/crap Google has on their page and in their browser!! I'm not complaining about the speed of Google loading, but if everyone was still using dial up, I'd bet there be more complaining about it then?

90% of the reason I WILL NOT use anything Google!! It IS NOT the greatest thing since the wheel, or internet!! Google sucks green donkey d**k!!

How bad looking it was? What's bad about that? It's called simple and simplistic and it loaded very fast too, I bet, which is how I wish it still was instead of all the bloat/crap Google has on their page and in their browser!! I'm not complaining about the speed of Google loading, but if everyone was still using dial up, I'd bet there be more complaining about it then?

Nowadays version is minimalistic and loads almost instantly.

Just when you couldn't hate mozilla any more than you currently do.

They go and change this, which adds zero benefit but ****s every standard up.

Oh way to go...

What utter tosh. Why not actually read the bug ticket? UA strings are hardly a strict standard, as it is (and have a loooad of historical complexities around them). Sites should be feature sniffing, not browser sniffing. Do you have much experience with how UA strings work?

As it is, it's not going to stay broken/weird for long. Google is likely thinking the browser version is much older than it is.

"Sites should be feature sniffing, not browser sniffing. Do you have much experience with how UA strings work?"

Guess you've never been a web developer in your entire at all then.

Javascript comes with chome, firefox, etc. yes. A lot of browsers do not have javascript support (lynx, links, etc.), or have it disabled (no$cript).

This is just plain badly written code on Google's behalf, instead of checking for the version of the browser they check for the date it was compiled on, which is pretty damn meaningless (You could have a lower version with a higher build date, etc.) There's a reason Mozilla froze that date to be 2010-01-01 with 4.0, to discourage this, Google is just apparently slow to notice.

Edit: Ahh, I see the JS angle then. Still, your site shouldn't rely on JS to function and this is a server side issue on Google's behalf, not a client side issue.

"Sites should be feature sniffing, not browser sniffing. Do you have much experience with how UA strings work?"

Guess you've never been a web developer in your entire at all then.

Javascript comes with chome, firefox, etc. yes. A lot of browsers do not have javascript support (lynx, links, etc.), or have it disabled (no$cript).

It's not an either/or situation, though - browsers inherently without JS support could still be UA detected. I don't have much sympathy for people who would noscript Google - of course you're going to lose features that way. Just like if I turn off CSS, sites will also look fairly weird - but I'm not going to complain about it. (Turn off the scripts you don't want to run, for sure, but turning off *all* scripts and expecting everything to be okay is over the top)

There's many articles online about browser and feature sniffing, and the benefits of each - but they pretty much always come down on feature sniffing. I know browser sniffing is commonly used, but that doesn't make it good.

Besides, that's not a defence of your original comment at all, which was that somehow it was all Mozilla's fault.

This topic is now closed to further replies.
  • Posts

    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
    • Thanks for the advice guys, I'll give my current GPU a clean and then run the benchmarks to see how similar it is. Hopefully a bit of a clean-out will help it last a bit longer.
    • Pretty sure those will still be in this game. The series' well-explored psychosis themes will return as well.
    • "performance issues? what performance issues?!"
    • Microsoft making much needed change to Windows 11, 10 Patch Tuesday security updates by Sayan Sen Recently, Microsoft delivered its latest Defender patches for Windows 11 ISOs. These definitions are released from time to time alongside the general security updates available during Patch Tuesday. Speaking of Defender, the company has now announced another important change that affects how security updates are delivered to enterprise devices running Windows. According to a recent announcement, Microsoft Defender for Endpoint's endpoint detection and response (EDR) updates will no longer be bundled with the monthly Windows security updates or Patch Tuesdays. Instead the company is shifting delivery of these updates to Microsoft Update, bringing EDR servicing in line with several other Microsoft Defender components. If you recall, Microsoft last year moved PowerShell updates to Microsoft Update (MU) as well since it provides automatic updates for Microsoft products and services. Thus the move is intended to allow Microsoft to deliver EDR improvements and security enhancements independently of the OS's regular monthly update cycle; this should enable faster deployment of protection updates without requiring organizations to wait for the next Patch release. For those unfamiliar, Microsoft Defender for Endpoint's EDR capabilities are designed to help organizations detect, investigate, and respond to advanced threats across managed devices. Keeping these components updated is critical for maintaining protection against evolving attack techniques. The rollout has already began for Windows 10 devices in late May 2026 (last month) and Microsoft says it will gradually expand support to Windows 11 and the remaining supported Windows versions over the coming months. The company expects deployment across Windows 10 and Windows 11 to be completed by fall 2026 or around Q3 of this year. Once the transition is complete, EDR updates will be delivered through Microsoft Update using KB5005292, provided the required prerequisite updates have already been installed. Microsoft is also introducing a new Defender Update Service as part of the change. Following installation of the first update, devices will automatically create a new directory located at %ProgramData%\Microsoft\Microsoft Defender\Defender Update. Microsoft notes that restarts may occasionally be necessary in case of "rare" failure scenarios. For most organizations, the tech giant says no action will be required as long as Microsoft Update is already permitted within their update management strategy. Admins who rely on manually deployed update packages, however, will need to adjust their processes to ensure the new Defender update package is included. Microsoft also recommends reviewing internal documentation and notifying helpdesk and security operations teams about the updated delivery mechanism to avoid confusion during the transition. As a prerequisite, the tech giant notes that systems must be running Sense version 10.8798.25857.1000 or later and have one of the following Windows updates (or later) installed: Win11 24H2 KB5062660 (2025-07 Cumulative Update Preview) Win11 23H2 KB5062663 (2025-07 Cumulative Update Preview) Win11 22H2 KB5062663 (2025-07 Cumulative Update Preview) Win10 22H2 KB5062649 (2025-07 Cumulative Update Preview) Win10 1809 KB5063877 (2025-08 Cumulative Update) Server 2019 KB5063877 (2025-08 Cumulative Update) Server 2022 KB5063880 (2025-08 Cumulative Update) Server 2025 KB5063878 (2025-08 Cumulative Update) As always, organizations should verify that their update policies align with the new servicing approach before the broader rollout reaches all supported Windows platforms later this year. In case of major problems, the EDR update can be rolled back to the inbox version stored in %ProgramFiles%\\Windows Defender Advanced Threat Protection (ATP) using: MpCmdRun.exe -RevertMde -Product Edr -ToVersion Inbox For those who have access to the Microsoft 365 Admin Center portal, you can view the message here under ID MC1381119.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Steven P.
      73
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!