No text appears when loading the blog on Chrome for the first time

Have the same, just not the event error.
Only on Chrome. Switched off all other plugins.
Only have this effect, when Background Manager (BG) is activated.
Just deactivated BG in the meantime.

Have the latest WP version + Twenty Twelve.
What am I doing wrong?

I can confirm that behavior on Chrome (Windows, Android).

The text is there, but somehow invisible – it can be marked, is then still invisible, but can be copied & pasted. If you hit a link, the next page is displayed correctly, until you reload (F5 or manually), then the problem occurs again.

Disabling background manager immediately fixes the problem.

I did a bit debugging and found the cause of the problem. As i am not a JavaScript developer and Myatu’s code is really hard to understand without working in it, following fix is not a real fix. It can break things, kill your cat and cause thermonuclear war. If you want to use, use it, but i take no responsibility for fucked up things. Make a backup.

As far as i understand this, the disappearing text is caused by when the flux.js checks for 3d-transition compatibility. if this is true, it tries to modify the html, which, i assume gives Google Chrome some headaches -> text disappears.

So the fix is the deactivation of the sourcecode-modification, which applies to all webkit-bases browsers. there SHOULD be no effects on other browsers like Firefox and IE.

The fix:

open wp-content/plugins/background-manager/resources/js/flux.js in a editor of your choice. Make a backup first.
The code is obfuscated and in a single line, so it’s readibility is bad. But that’s not important, as you only add a //

Search for the following:

[code]
b("head").append(f);
[/code]

add a // before to comment that code out. Do not change any other things.

it should look like this:
[code]
//b("head").append(f);
[/code]

Save. Upload. Try Chrome ??

As said, this can break some other things. Basically, maybe 3D-Transitions will not work. Hopefully, Myatu will fix this much better ??

Whoops, sorry, here again the code parts:

search:

b("head").append(f);

add // before, should look like this

//b("head").append(f);

Whoops #2

Sorry, this breaks the code, it comments all the following code out.

Here is the correct fix (this time for real):

search:
b("head").append(f);

replace it with:

/**b("head").append(f);*/