The thing is, code will react differently from Mac to Mac as well, so just having an emulator or a single Mac may not be all that much more useful than a port anyway. If you require more than that, you should acquire a Mac, preferably one that typifies the Mac environment you want to write for. If you write valid code, keep things as simple as possible, use object rather than browser testing in scripts, a port of the browsers you are targeting should be all that is required for testing. If you need more speed or move between iOS, Android, and Windows, you may want to look. Safari 3 Win has helped me tremendously though in at least getting the broad strokes of my code into line with what Safari can handle and to see how it will (generally) look. a port of the browser(s) run under Windows. However, I've heard some strange things about even FF on a Mac, so I'm not confident that running an emulator would give you all that much more than Safari 3 Win, as subtle quirks would almost invariably be different on the Mac vs. It will not help you a lot for folks using older Safari versions, though some of the rendering and script quirks are preserved. As I'm pretty sure you know, Safari runs on Windows now.
