K-Meleon :: General

General : K-Meleon Forum

General discussion about K-Meleon.

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

Your Name:
Subject:

Help information

[quote=siria]
Hey, cool video! :D No idea how you managed that, never happened to me. Perhaps the special characters somehow? Not really, if enter wasn't pressed, huh? But it's known that there are some bugs with urlbar in 1.6beta. Just not such spectacular crashes live on video, LOL! PS: deadlock figured out just days ago that in certain cases it's due to huge history files.

[quote=JohnHell]Old macros = new macros with different definition styles. They do exactly the same.[/quote]

How come I have a hard time believing you "exactly the same"? Ah yes - because the very same code lines work fine in a "normal" macro environment and not in a "legacy emulation" environment?? That's the only difference, or do you know another? If the code itself is the same?

[quote=JohnHell]I know, and that is why I find less than funny to find asking what reasons are to still using old versions.[/quote]

There's a wide range between 1.0 emulation and 1.6beta :cool: E.g. KM154 works quite well, apart from the increasing "outdated gecko" probs. But in yet older versions those probs certainly are more, not less.

[quote=JohnHell]When K-meleon gets stuck at 100% CPU load and the only way to continue using it is close it... what is the workaround? Please, tell me, because, right now, this is the most annoying thing with 1.6b2.[/quote]

Happens too rarely to me, and then mostly when I have some 30 tabs open in my oldie machine with 256MB RAM. My fault. And when 1.6beta gets stuck due to some script, I toggle windows for a second and it'S responsive again. As written before, I do have less plugins than others (no java for example), and usually all sorts of stuff blocked, incl. "DOMstorage" and "embedded objects". Hmm, when I think hard, there returns a memory about some fancy-blinky forum that used to kill KM if JS was on, but that was long before the first 1.6 version. Finally figured out it had to do with some stuff from "ajax.googleapis.com", blocked that in windows HOSTS file, and prob was gone :P But the bug as you describe it exactly is rather unknown to me, sorry. Yeah it does exist, have read about it from others too in this forum.

[quote=JohnHell]The first time I hear there is no need to enable javascript to use injectJS. And, hey!, it's true.[/quote]

Uffff.... ONE point gotten across, can't believe it, LOL! :D :D
No idea if it's written somewhere, I just noticed it some day. Took me just awhile to realize why it worked sometimes and other times not! Ah yes, guess I actually mentioned it myself a few times in the forum, when the subject was policy manager and the infamous caps policies. Then again, perhaps was only implying it, when posting that many default functions are blocked when using CAPS-JS-block, can't remember exactly, 
Yeah, it would easier be found on macrolanguage2 page. But frankly, how often and thoroughly you study that one??

About CAPS policies: 
[quote=JohnHell]But you told me. You assumed I was using it. Why? [/quote]

I didn't "assume" you use it, but it wasn't completely impossible, so better mention it too. It's one of two ways to block JS in gecko, and had no idea (before digging up my 1.0x version) which one a stoneage KM had used by default. Still possible that some macro uses it, but not very likely.

[quote=JohnHell]why now is not accepted "javascript:whatever_function_to_run();" as URL? [/quote]

[quote=JohnHell]But I don't toggle on-off continuously. Have a look, again, to my code. I just toggle on, inject code, let run code, toggle off.[/quote]

At first, yes, but then you posted about "javascript:whatever_function_to_run();" as [b][u]URL[/u][/b]. So that sounds as injecting the last part via URLbar now instead of via injectJS. If that was just a misunderstanding, all the better.

[quote=JohnHell]Never, never, can this kill a script. Unless the toggle off is being run before wait until script finishes. This behavior is correctly made by 1.1.x, why not in 1.6b2?[/quote]

It does work in 1.6b2, must be some other reason in your setup... :cool: :D BTW you mentioned jit, that's also one of the things I've disabled on my oldie machine.

[quote=JohnHell]What do you have against old macro definition if they do exactly the same?[/quote]

Oh nothing. Just can't help getting the impression that they don't quite exactly do the same in our 1.6b2 browsers. It works on mine. It works not on yours. "Exactly the same"?? *whistle*[/quote]

K-Meleon forum is powered by Phorum.