InformAction Forums

Hi,
I love my noscript, but there's a bug that's been bugging me for some time and it's about web bug blocking (pardon my puns).
As an example, there's this web page I've set up for a girl's footie team. Registered users get a scrolling display of the 5 newest users in the left column.

When the web bug blocking feature is enabled, those names get "eaten" by noscript, no matter if the site is trusted or untrusted.
I've created an account to do some tests if you're so inclined:
User: test Pass: tester

Thank you very much in advance!

Looks like a bug in the <marquee> element, which stops "accepting" children as soon as an image child is referenced by a content policy: in facts, you can check with DOM inspector or Firebug, the generated doom misses all the elements past the first IMG.
I doubt it will be fixed in Firefox, since <marquee> is deprecated. Could you rewrite that effect to use JavaScript instead?

First of all, thank you for looking into this!
The page is based on phpnuke which is a modular content management system and the scroller is one of those modules. phpnuke is not very popular anymore, so I doubt I will find an updated module.
However, I'm wondering why the web bug rule is still active when the site is marked as trusted - I thought this was a perfect case where the rule should not be applied at all?

Jorgo wrote:I'm wondering why the web bug rule is still active when the site is marked as trusted - I thought this was a perfect case where the rule should not be applied at all?

Very good point. I'll tweak the rule in this sense, also checking if the image domain is actually different than the page's, in next build.

You're da man - il uomo, even

Done in latest development build