Originally posted here by Tiger Shark
Whine, moan, complain, bitch, whine again, stamp feet, throw the toys from the pram, take bat and ball and go home......

The biggest thing I have learned since starting playing with computers all the way back in 1982 is that no matter who writes it software has flaws... omg .... It's what I was exploiting back then, what people are exploiting today and what people will still be exploiting when I die.

You kids need to get over this "my **** is better then your **** because [insert rubbish here] attitude".... Either be instrumental in making your **** better or be quiet.....

Fair?
Yes sir..fair enough

Btw I just testing my firefox
Firescrolling 2 - Proof-of-Concept
Designed for Firefox 1.0.1 | bugzilla #285438 | CAN-2005-0401 | Full Advisory

Even though Firefox 1.0.1 patched one of the key bugs behind my firescrolling exploit (the ability of plugins to load chrome files in a hidden frame) the ability to hijack a drag and drop operation and open a privileged xul file is still available.

The demo opens "chrome://global/content/alerts/alert.xul" when dragging the scrollbar the first time. This XUL file automaticly runs an inline script to turn the window into a tray notification alert. This demo is just an example of an annoying usage, but if the browser or an extension contains an inline script that uses an eval/setTimeout with a parameter an attacker can influence it turns into an arbitrary code execution bug. Also update or uninstall scripts could be a valuable target. I doubt most extension developers think about problems that could occure if a XUL file in their extensions is opened directly.
link http://www.mikx.de/firescrolling2/