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]
Have played with the same idea awhile back, when I found that gecko has a native system to handle exceptions lists by the "capabilities.policies" prefs ("CAPS"). Those prefs are intentionally hidden in about:config, only visible in prefs.js directly. 
So I made a little macro with menu, all in macrolanguage, that adds pref-toggling and white-black-list stuff to the javascript-button. No GUI, just menu that pops up a prompt line for input/editing. Sort of a very primitive policies manager, as it was perhaps in version 0.1alpha ;-)

That macro was experimental, still sitting somewhere on my harddrive, but the one crucial problem remained: There are just 2 "general" javascript blocks, one by capabilities (which handles black-white-lists, but unfortunately blocks all native KM commands which are based on JS, like guess zoom options), and the other general JS setting from privacy menu, which ignores the whitelist!

So if you're willing to have [i]JS *active* by default, and only use a little blacklist[/i], you could start out playing further with that macro. But if JS should be blocked by default, it's useless :( If several pages are loading at the same time, ALL would be allowed JS, or the other way around, lots of other useful macro commands will stop working.

A little bug: Just yesterday discovered, while playing with another macro, that pref-editing (BW-list) via prompt line only accepts lists of up to 255 characters, didn't know that yet! The prefs can hold much longer values, just not input via prompt line. So would have to add the workaround of copy/pasting longer lists via clipboard and notepad, like in my other macro.
Ah yes, and have quite some notes in that macro for more probs! E.g. the CAPS BW-list doesn't judge by the origin of a script, no, third-party scripts can have their source anywhere and are still allowed, if the current page url is whitelisted! Or only complete domains are toggled, no sub-domains possible as exception. And so it went on... Have it given up.

--> Long live the privbar! :D 
Like it best anyway, JS-state always clearly visible, no gray cells needed for remembering exception sites :)

Then again... there was also some way to handle BW-stuff in [b]HOSTS-file[/b], perhaps that's better?? But the KM hosts file doesn't work in 1.6 anymore (guess due to gecko changes) And even the windows hosts file doesn't seem to fully work in it anymore. Have a KM menu line to simply open that one in notepad, the ultra-basic-mini solution ;-)

Oh well, can't swear on all that stuff above any more, been too long, have too much forgotten of it meanwhile :([/quote]

K-Meleon forum is powered by Phorum.