Body with class "not-ready": white windows

uli · 2018-01-14 18:42:49

I’ve installed today for the first time a current 4.7 Nightly (ca35d2b55fd5aff59013dac0bcdaeaa3). In one FF the body has class “not-ready” (white page for opacity=“0”), another FF (same version but no extensions) displays the body. Are there any reasons why this TXP version behaves like that?

Edit: This one FF seems to be the only one with class not-ready, BTW. All other tested browsers and FF instances don’t have that behaviour.

Edit 2 after transferring topic to “Troubleshooting” : I’ve now disabled all extensions and disabled cache, but no changes. Where else can I drill?

Last edited by uli (2018-01-14 19:51:03)

phiw13 · 2018-01-14 22:28:29

uli wrote #308667:

In one FF the body has class “not-ready” (white page for opacity=“0”), another FF (same version but no extensions) displays the body.

The class is normally removed on `dom-ready` or something

enable debug in the TXP install
check the console in Firefox for possible JS errors

Same version of Firefox?

philwareham · 2018-01-14 22:36:13

Empty/refresh the cache?

phiw13 · 2018-01-14 23:06:31

Also – remove any cookie and local storage data for that domain.

local storage can be removed from the “storage” tab in the developer tools.

uli · 2018-01-16 12:40:51

Thanks for your help, guys! For whatever reason, local storage was turned off, and 4.7 uses that feature, different from 4.6.

Bloke · 2018-01-16 12:47:33

uli wrote #308689:

local storage was turned off

Wasn’t aware it could be turned off! Is our reliance on it going to cause a problem? Or do we need to state it’s a requirement – the same as enabling cookies is a requirement, otherwise you’d need to log in every time you clicked an admin-side panel.

etc · 2018-01-16 12:49:51

uli wrote #308689:

For whatever reason, local storage was turned off, and 4.7 uses that feature, different from 4.6.

That’s weird, localStorage is already used in 4.6, though we have added new data in 4.7…

phiw13 · 2018-01-16 12:50:55

uli wrote #308689:

For whatever reason, local storage was turned off, and 4.7 uses that feature, different from 4.6.

Uh, I didn’t know either that you could turn it off. And yes, as far as I understand it , 4.7 uses it more than 4.6. depending on which panel you land, that might cause problem (Oleg will know …)

uli · 2018-01-16 13:02:33

etc wrote #308691:

That’s weird, localStorage is already used in 4.6

Ah, you are right: I just saw I made a diff between 4.5.7’s JS file and the 4.7 one.

I’ve fiddled and tweaked some settings in about:config for privacy/tracking reasons.

Bloke wrote #308690:

Or do we need to state it’s a requirement – the same as enabling cookies is a requirement

I guess there are more folks conscious about cookies than about local storage. But hinting at possible problems is always a good thing, I think. But I might be biased here ;)

etc · 2018-01-16 13:04:26

Should be patched now, with localStorage disabled settings are not remembered, but, at least, you don’t get a blank page (sorry for that).

uli · 2018-01-16 13:38:29

OK, I should be a little more precise so no fault creeps in: The setting I altered is named dom.storage.enabled. Sorry for any inconvenience I might have caused.

Textpattern CMS

Textpattern CMS support forum

#1 2018-01-14 18:42:49