Moin Benjamin!
Benjamin Mesing schrieb am Montag, den 22. Oktober 2007:
> The problem still persists. I've managed to track it down to the
> filter{js-annoyances} rule.
Okay, that may be the cause for filter{js-annoyances} being disabled
in all standard profiles (cautious, medium, and advanced). Simply use
the default settings and everything is all right. If you think you
need filter{js-annoyances} to be enabled, you have to live with the
implications including maximum cpu load on some sites.
As a work around, I suggest adding something like this to your
user.action file:
{-filter{js-annoyances}}
www.memo.de
Tschoeeee
Roland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
