Do the exploits which lock up or crash Windows Firefox do the same thing to Mac Firefox? The sort of thing I mean is making the browser print iframes, declaring an anonymous function in a loop, setting up multiple mailto tags, setting up huge numbers of input tags or enormous tag sizes, and multiple nested object or marquee tags.
Is Safari susceptible to content-disposition in inline mode forcing a file to be either opened or executed (as is Internet Explorer)?