4 ms·

This page came up for me blank... I had to stick it in brave for it to work. I guess google doesn't make web pages anymore...

jeroenhd 2y ago
Ad blockers get really weird with Google blog pages, especially if you use multiple or very strict ones. There are plenty of rule lists where most Google domains are just blacklisted by default in case something tries to load javascript from them, and those will break the blog posts. Page works for me, but the CSS is screwed up by adblock. It is what it is.
wging 2y ago
In what browser did it fail to work? It works for me in both iOS Safari and desktop Firefox.
- tom_ 2y ago
  Comes up blank for me on Firefox 129.0.2 and Firefox 130.0, both on Windows. I don't use ad blockers.
monocasa 2y ago
Comes up essentially blank for me too on Firefox desktop on ubuntu 24.04. Still comes up blank with the only adblocker I use (ublock) disabled as well.
- Gigachad 2y ago
  Loaded fine for me on Firefox on Macos
freedomben 2y ago
I had to whitelist a script from ajax.googleapis.com to get the page to load.
tlavoie 2y ago
It was blank for me on Firefox, even with uBlock origin turned off. However, disabling JavaScript on the page did the trick! So, whatever shenanigans they're doing to mess with the page rendering are completely unnecessary for the reader.
- DoingIsLearning 2y ago
  Didn't disable JS but got an instant page load just from putting the page in Reader mode. A blog entry text page shouldn't be this hard.
  - tlavoie 2y ago
    Oh, I hadn't thought to reach for Reader mode, that's a good point for people who are using closer to a stock config. Of course, rendering a text blog page should be trivial, but... Google. I expect little different there.
- littlestymaar 2y ago
  The problem comes from an error in JS, that's why disabling it makes it work I guess: > Uncaught InternalError: too much recursion
dartharva 2y ago
Same for me. It was going on for quite some time, but guess it has started with full force now. Google will now steadily turn Firefox useless by having everything break on a non-Chromium browser.
Kostarrr 2y ago
It was blank for me as well until I reloaded with dev tools open and cache disabled. Figured it was a caching issue but maybe something more weird?
goodpoint 2y ago
That says a lot about google's efforts at monopolizing the web.
billforsternz 2y ago
Ironically, if it does work it manifests as straightforward text with tasteful styling. It could be implemented with bare bones techniques.
deleted 2y ago
[deleted]
deleted 2y ago
[deleted]

jeroenhd 2y ago

Ad blockers get really weird with Google blog pages, especially if you use multiple or very strict ones. There are plenty of rule lists where most Google domains are just blacklisted by default in case something tries to load javascript from them, and those will break the blog posts. Page works for me, but the CSS is screwed up by adblock. It is what it is.

wging 2y ago

In what browser did it fail to work? It works for me in both iOS Safari and desktop Firefox.

tom_ 2y ago
Comes up blank for me on Firefox 129.0.2 and Firefox 130.0, both on Windows. I don't use ad blockers.

monocasa 2y ago

Comes up essentially blank for me too on Firefox desktop on ubuntu 24.04. Still comes up blank with the only adblocker I use (ublock) disabled as well.

Gigachad 2y ago
Loaded fine for me on Firefox on Macos

freedomben 2y ago

I had to whitelist a script from ajax.googleapis.com to get the page to load.

tlavoie 2y ago

It was blank for me on Firefox, even with uBlock origin turned off. However, disabling JavaScript on the page did the trick! So, whatever shenanigans they're doing to mess with the page rendering are completely unnecessary for the reader.

DoingIsLearning 2y ago
Didn't disable JS but got an instant page load just from putting the page in Reader mode. A blog entry text page shouldn't be this hard.
- tlavoie 2y ago
  Oh, I hadn't thought to reach for Reader mode, that's a good point for people who are using closer to a stock config. Of course, rendering a text blog page should be trivial, but... Google. I expect little different there.
littlestymaar 2y ago
The problem comes from an error in JS, that's why disabling it makes it work I guess: > Uncaught InternalError: too much recursion

dartharva 2y ago

Same for me. It was going on for quite some time, but guess it has started with full force now. Google will now steadily turn Firefox useless by having everything break on a non-Chromium browser.

Kostarrr 2y ago

It was blank for me as well until I reloaded with dev tools open and cache disabled. Figured it was a caching issue but maybe something more weird?

goodpoint 2y ago

That says a lot about google's efforts at monopolizing the web.

billforsternz 2y ago

Ironically, if it does work it manifests as straightforward text with tasteful styling. It could be implemented with bare bones techniques.

deleted 2y ago

[deleted]

deleted 2y ago

[deleted]