Sure, that couldn't hurt. I've actually tested it on Mac/Firefox and Mac/Safari (albeit an earlier version of Firefox) and it's worked for me. So I think it's less likely a straight-up browser/OS issue, and more likely an interaction with either the monobook.js or perhaps another piece of Javascript code that may be running on your client. But that's just a guess. If it behaves differently for you with Safari, please let me know. '''''' Talk