K-Meleon :: Bugs

Bugs : K-Meleon Forum

You can talk about issues with k-meleon here. But please, for confirmed bugs, use the bug tracker to report and give feedback on bugs.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=rodocop]
[b][color=#FF0000]IMPORTANT![/color][/b]

It seems like I've found the reason of keyboard unresponsibility, and - a shame for me - one part of this follows from my own recommendations ¬_¬

So now I give you corrected settings.

[code]
[list]
[*] user_pref("content.interrupt.parsing", [b][color=#CC0000]true[/color][/b]);
[*] user_pref("content.max.tokenizing.time", [b][color=#CC0000]600000[/color][/b]);
[*] user_pref("content.maxtextrun", [b][color=#CC0000]2048[/color][/b]);
[*] user_pref("content.notify.backoffcount", [b][color=#CC0000]10[/color][/b]);
[*] user_pref("content.notify.interval", [b][color=#CC0000]120000[/color][/b]);
[*] user_pref("content.notify.ontimer", [b][color=#CC0000]true[/color][/b]);
[*] user_pref("content.switch.threshold", [b][size=medium][color=#FF0000]900000[/color][/size][/b]);
[/list]
[/code]
The last one is the key. When I've reduced it to 300000 (0.3 sec) KM simply started to get into low frequent interruption mode (unresponsive while parsing pages) too quickly, so the time between pressing first and second button in hotkey combinations (like [color=#990000]Ctrl[/color] + [color=#990000]F4[/color], for example) became generally bigger than this interval (0.3 sec).

So, I recommend to increase it up to 900000 (0.9 sec) or slightly more - and key response gets back!

And one more clarification about settings:
[code]
user_pref("javascript.options.jit.chrome", [b][color=#CC0000]false[/color][/b]);
user_pref("javascript.options.jit.content", [b][color=#CC0000]true[/color][/b]);
[/code]
Both are default settings (if they exist in your config) and you should check these are set so.

jit settings are controlling TraceMonkey - js-engine, appeared in FF 3.x. 
[b]jit.chrome[/b] option controls using this engine in GUI rendering.
[b]jit.content[/b] - in content rendering respectively.

KM doesn't use slow XUL GUI of FF, so this option ([b]jit.chrome[/b]) must be set at [b]false[/b].
I think, this also speeds up UI response.[/quote]

K-Meleon forum is powered by Phorum.