: K-Meleon Forum
General discussion about K-Meleon.
[quote=siria] Oops - Darn, first major bug found, and it's my fault!! :-( Had not intended it at the time for publishing, was only half-way finished yet. And now last week didn't spend much time on checking it again. But now when looking at your mini-version, it downright jumped into my eyes! [b]BUG[/b]: The first line without # (after startup) [color=red]deletes a possibly already existing list of various policy zone names![/color] (could have been created by PolicyManager or other) Yes, you just copied the bug that was already in my long version. That's a bit dangerous really, although it can be fixed with Notepad: opening prefs.js while the browser is closed and complete the zones list again manually. But who knows what other bugs may be in it still?? Cannot spend too much time on it currently, and see no real future for it. Perhaps for a mini-version some day, might be, but have not enough time currently. The main (huge) prob is that it can interfer with other CAPS-zone-macros. Simple example: how are the zones names separated in the list?? Can be either blanks or commas acc. to Mozilla. So if one macro uses blanks and the other commas, it produces a mix, and I doubt that would work well :-/ And is there this separation character also at the end, or not? And how about the beginning? Yes it basically works - but only as long as no other such macro is used. The real challenge would be to avoid all imaginable side-bugs when interfering with them (especially policy manager), Please snuz, mark the mini-version clearly as "[b][u]Experimental[/u][/b]" too, in the posting and inside the kmm as well. I'd also prefer to make yours completely independant from my "sitelist", that means renaming all the "sitelist" and "JSS" to your own name, which is fine. Some you have replaced already, but not all. In the kmm you could write something along the lines of "by snuz2 (based on experimental macro by siria)" or such. Hope it's okay for you. You can replace the first buggy line with: [color=blue]$_zones=getpref(STRING, "capability.policy.policynames"); if (index($_zones,"jsblacklist")<0) setpref(STRING, "capability.policy.policynames", $_zones."jsblacklist, ");[/color] But there it starts again: What if there's already an existing zone named e.g. "myjsblacklist" or "jsblacklist5" etc.?? What if an existing list ends without separation character? Should I add a blank, just in case, or perhaps a blank+comma?? Would take quite some coding to first examine and check the current syntax before adding more zones. Sigh. Or perhaps merely check if there is ANY list existing yet? if($_zones=="") ... At any rate it takes quite some work yet. Ah yes, here's a link to the Mozilla page, how their CAPS policies work exactly: http://www.mozilla.org/projects/security/components/ConfigPolicy.html[/quote]
K-Meleon forum is powered by