kb.vmware.com/s/article/1023856 yay VMWare

the KB renders blank pages except for a "Support Assistant"balloon

the console registers a bunch of noise from their framework, "Aura"

including a unhelpful "TypeError: header is null" (logged by them!)

also the actual page sourcecode contains NOTHING that could be extracted back to something readable, it's all JavaScript down there!

Many websites nowadays just refuse to work if the browser is not "whitelisted"

so this is why those VMWare KB pages actually work through the Google cache

except that these days, Google tends to hide the "view cached" button

Where did they move it?

it's hidden behind a dropdown arrow in the little info box that opens if you click the 3 vertically stacked dots next to the page URL in the results header

note, this only applies for this week

maybe by next week it's completely gone, or misplaced

google cached button has never worked for me

how did u guys make it work?

first you have to pretend you're "recent Firefox"

otherwise GOOG will serve you cellphone pages

i never see any "view cached" behind the 3 dots. only some more options panel which is meaningless tbh

franstam: on that panel there is a "V" in a circle

click that

just discovered it today

oh now i see it

thanks

bullshiet tbh

Move! Fast! And! Break! Things!

is goog scared that we find their sekret cache?

scared that we use up all their bandwidth?

the problem is that cached pages get special treatment from the source servers by dropping down a notch or then on the JavaScripts

for example the VMWare KB serves perfectly flat pages to Googlebot

and encrypted JS framework vomit to the rest of us

and of course, we MUST eat the JS framework vomit, NO EXCEPTIONS, hence why GOOG now pretends the cache is gone

oic

its just to hide their incompetence

makes purfect sense

i dont mind mobile pages tbh. less js vomit u say

give me mobile pages then

Sompi: I can read fingerpori, but hesari's front page indeed blanks to me if I have javascript enabled :-\

Sompi: usually I think this kind of thing suggests a coding error or lack of error handling in the javascript code

"JavaScript error: hs.fi/_next/static/chunks/main-b8e2658307c68cb0.js, line 1: TypeError: e is undefined" for the front page.

all praise the minified JS gods, who brought us meaningful line numbers

tomman: lol. This makes VMWare KB serve content too: Mozilla/4.0 (compatible; MSIE 6.0b; Windows 98)

I'd love mobile pages, except google pushed somewhat to have "js vomit" and "css with lots of whitespace" be the new "mobile page"

now back to .fi - what else is broken besides hesari? All of Sanoma? More than Sanoma?

at least one site from Alma and one from Savon media appear to load fine, but maybe I'm just checking the wrong pages

Ilta-Sanomat (Sanoma) blanks, Ilta-Lehti (Alma) does not blank

in fact, ilta-sanomat blanked while displaying the cookie "popup"

as in, it still showed the popup, but the page was already blank

aamulehti.fi blanks, also with a Sanoma cookie "popup".

turun sanomat and kauppalehti load OK too

so far: seems to work without javascript; seems to happen only on sites managed directly by sanoma media, but it might be that I'm not looking widely enough

it seems to involve performance.measure, toggling the settings didn't change it, could it be that they have the same issue as Google Translate full-page translation (requiring the new performance.measure spec) *but* don't have a fallback at all if performance.measure is not present?

njsg: Those errors in the console also come up with Firefox but the page doesn't blank

Sompi: same typeerror on the same js file? can you get the column number in the devtools inspector for firefox, just to make sure it's the same?

the column number put me in a place where it's doing performance measurements, so that's why I assumed it was that

of course life would be no fun if issues were always that simple to identify

Does it work on Seamonkey if the user-agent string says that it is Firefox?

I didn't try with a "newest firefox" UA, just some firefox UA, possibly too old, that didn't work

"identify as firefox" didn't help

These are just news sites with mostly text content and some images. They should work on all browsers...

also, why is this not happening everywhere on the sites?

I think a fingerpori strip didn't get blanked

works too: hs.fi/viivijawagner/?ref=snavi

Some random minified javascript library probably blanks the page if some unknown-to-us conditions are true

And things like these are extremely hard to debug as a browser developed

developer*

I'm thinking of how I'd like to approve network interaction by network interaction in devtools, kind of like Windows 4.x interactive config loading

And the page may actually be working just like intended. They are breaking it on purpose if someone uses a browser that they haven't heard about

but to be fair it'd just be quite simpler if the javascript weren't minifed and so on

my guess is that this is more "but what do you mean browsers might not support [this] or [that]? it has been in [browser I use] since [X time ago], why would anyone use anything older than that?" "you know there are browsers beside [one] and [another], right?" "what, lynx?", but could as well be intended breakage too

Most websites nowadays have literally megabytes of minified javascript, and the page itself doesn't have any contents that couldn't be shown with static HTML and CSS...

It is crazy. I wrote an operating system that can go online and host a HTTP server, and it has much less code than an average website has nowadays. And the code isn't even minified

oma.sanoma.fi/aihe/yhteystiedot fails too, but the weather section of Hesari (which redirects to IS?) works.

njsg the site uses dynamic imports. I am on it but not around the corner. My updated SpiderMonkey dislikes the new regexp patches.

one of the pages that does not blank had a message about "ad slot cover not found", but maybe that's just a coincidence

well, it IS relevant - for the FOUNDATION (cause they have to do /something/ to support their existence), but there is no relevance, otherwise, to me or you or to anything browser related