Bugs :  K-Meleon Web Browser Forum
You can talk about issues with k-meleon here.  
Rendering Problem (?)
Posted by: Tnebi
Date: February 01, 2015 03:25PM

Hello I tried to load this website on my pc and on another pc with the same version of KMeleon (74) and it keeps me gettings the page not loaded as it should.The website is http://www.bitdefender.it/
I tried loading it with any other browser I do have (even QtWeb) and it works. So I'm wondering what is causing this (Gecko rendering?)

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: Zero3K
Date: February 01, 2015 06:28PM

I am able to replicate this bug.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: rodocop
Date: February 02, 2015 02:18AM

Only naruman's latest KM74+1 renders it correctly.

All other KMs including latest KM75b2u1 - failed.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: Tnebi
Date: February 02, 2015 12:25PM

So this means there's a plugin allowing the rendering into the naruman build right?

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: rodocop
Date: February 02, 2015 12:34PM

naruman's release leaves more from full xulrunner used by FF, then official KM - some components here were cut out.

I think that is the reason - and only naruman and Dorian could find out, what is the missing one.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: Dorian
Date: February 02, 2015 05:59PM

It looks like it's related to CSP which I'm not familiar with, so I don't know

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: guenter
Date: February 02, 2015 08:54PM

Quote
rodocop
naruman's release leaves more from full xulrunner used by FF, then official KM - some components here were cut out.

I think that is the reason - and only naruman and Dorian could find out, what is the missing one.

naruman's folder ./browser is unpacked IMHO that is the big difference.

So I think the problem is about the compression of the omni.ja in browser.

Can someone rename the folder ./k-Meleon/browser (so that he does not lose it). Then unpack the attachment of this post and test it as new browser folder.
It seems to contain a lucky packed file. Or some other oddity that makes it work. I have no idea what caused it but it works here. So it may work on another system too.

p.s. I packed naruman's folder ./browser/modules into a standard
./browser/omni.ja. By chance it worked. Then I deleted one modules file after the other. Each time i deleted the profiles folder. And I tested. Finally I was there with a folder that still worked. It seems to have no more than the standard content.

So I do not know why it works on my system in several test installs.
Maybe my old XP?



Edited 1 time(s). Last edit at 02/02/2015 09:01PM by guenter.

Attachments: browser.7z (465.8 KB)  
Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: Yogi
Date: February 03, 2015 09:40AM

It works!
Tested with K-Meleon 74 and K-Meleon 75b2_u1 on Win7x64.





Edited 1 time(s). Last edit at 02/03/2015 09:46AM by Yogi.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: Tnebi
Date: February 03, 2015 10:02AM

Ye basically it's one file into the ./browser directory because now it's working well. Maybe we should wait for naruman to check it.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: Tnebi
Date: February 03, 2015 10:13AM

Ok guys I've made some tests and it seems that the Mozilla .js it's the file doing the work. Can someone please try to add only this file into the ./browser/defaults/preferences folder?

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: rodocop
Date: February 03, 2015 10:57AM

Mozilla.js is the main container for gecko prefs (settings which fill about:config page and manage all the stuff in mozilla-based browsers) so it's rather clear why this works - probably KM without this file misses some prefs to work right.

UPD.: Finally tested - mozilla.js does the trick!
For some reason this file is missing in Dorian's builds 74.0, 74-31, 75b1 and 75b2 along with i10n.js.



Edited 2 time(s). Last edit at 02/03/2015 11:11AM by rodocop.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: Tnebi
Date: February 03, 2015 11:20AM

I'll try to see which command line does the trick smiling smiley.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: rodocop
Date: February 03, 2015 12:20PM

It's not necessarily as all the mozilla.js is needed for proper operation of Gecko (xulrunner) engine.

Some prefs (number of) are redundant for sure, but we still need a lot of these prefs.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: JohnHell
Date: February 03, 2015 02:47PM

Come on guys!! we are experts on these tasks winking smiley

Just 2 seconds to find it:

security.csp.speccompliant set to true

I only searched for "poli" string trying to find a policy definition of a preference and I found these lines:

// Turn on the CSP 1.0 parser for Content Security Policy headers

pref("security.csp.speccompliant", true);

I tested this in K-meleon 74, so in K-meleon 75 should work too.


P.S.: I also found the CSP thingy in the error console window but didn't know how to manage. I found that it was working in GRE 31 (Firefox 31) but as I stopped using Km75 I didn't test as I thought it was a GRE version issue.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: JamesD
Date: February 03, 2015 05:15PM

Quote
JohnHell
pref("security.csp.speccompliant", true);

That seems to work.

KM75 b2u1 -- and that was the only change that I made.

Options: ReplyQuote
Re: Rendering Problem (?)
Posted by: guenter
Date: February 03, 2015 09:38PM

Quote
JohnHell
Come on guys!! we are experts on these tasks winking smiley

Just 2 seconds to find it:

security.csp.speccompliant set to true

No You are. tongue sticking out smiley

Great find. WFM. Made me find out why my upload works. It has the pref.grinning smiley

Options: ReplyQuote


K-Meleon forum is powered by Phorum.