I figured out how to fix it. Its an issue with OMTC (Off Main Thread Compositing). It can be fixed by disabling layers.offmainthreadcomposition.enabled via the about:config page.

I come back to this issue.

There is a black page for a moment, when an URL is opened in a new tab.


The effect of the fix above is, that the new tab is displayed later.
Instead of the black page you see the current tab longer.


Is there no way to change the black color to white?
This problem was not in KM 75.


Thanks
Michael

no idea, just curious - try that?
The general color for all pages which don't have an own bgcolor defined
browser.display.background_color = white (or #ffffff)

I think I answered along the years a few times about this issue.

If you see a black background the cause is, most probably, caused by the hardware acceleration not being supported.

Toggle in about:config the preference "layers.acceleration.disabled" to true, restart, and find if you see some changes.

Setting layers.acceleration.disabled to true did not make a difference.

btw, OS is Win XP SP3.

Is there no way to avoid the black screen?
Or at least change its color to white?

It occurs also on Windows 7.


Thanks
Michael

@Michael
You can search forum for "black screen" to find an answer.

There is nothing new at the posted link.

Moreover, I referred to this answer at the beginning of this thread.

So is it still happening in latest KM-Goanna...?
(the topic title says 76beta, was 3 years ago)
Looks like Firefox also has/had often a black-screen-prob, no wonder using the same engine. And the same prefs.

Just posting here the usual 3 discussed prefs together, for disabling hardware acceleration if black screen probs. Doesn't help always everyone, but many:

layers.offmainthreadcomposition.enabled => false
layers.acceleration.disabled => true
gfx.direct2d.disabled => true

And webgl is mentioned sometimes, should be ON

And a Firefox32 user on bugzilla once had success with the opposite, force-enabling everything! But one never knows, just mentioning, if anyone wants to play with those too:
gfx.direct2d.force-enabled => true
gfx.font_rendering.directwrite.enabled => true
layers.acceleration.force-enabled => true

For many people it just helped to update their graphics drivers.

Thanks for the summary, Siria.

Yes, still a black screen with lastest KM Goanna. (on Windows 7)


The only pref which shows an effect is:
layers.offmainthreadcomposition.enabled => false

But instead of a black screen I see the current tab longer, which is still irritating, in a different way though.


The other mentioned prefs did not make any difference on my system.

Also tried more or less everything suggested here. No help. Also Win7 64bit.

How can I access about:config when I only see a black screen?

Closing K-meleon and editing prefs.js adding the preference and its value as (adding if the preference isn't already there, or changing if it is), or in user.js (this, resetting its value on every K-meleon restart to the one in this file)

user_pref("preferencename", value);

Value being between quotes if it is a string (not BOOL (true or false); not an integer aka number).



Edited 2 time(s). Last edit at 11/17/2020 10:44PM by JohnHell.

Thanks again, siria and JohnHell

I manually added "layers.acceleration.disabled => true" to pref.js and that did the trick for me

Quote
Michael Sattler
Setting layers.acceleration.disabled to true did not make a difference.

btw, OS is Win XP SP3.

I did it and now I can see Uphold, but the websites needs too much resources and the PC stone, I must close k-meleon and restart it.