bah ....stupid Mozilla Firefox boneheads

I heard about this awhile ago, before Moz 1.7 was even released, and I recall a workaround that was very effective - but All I can recall is that it had to do with editing one of the JAR files in the %ProgramFiles%\mozilla.org\Mozilla\Chrome DIR (which in 2K\XP and Firefox will or may be an different location) -- some little tweak within, which I had incorporated at the time.

Now - I see that the developers want you to use about:config (as I have just tried, with the results shown above/below ) and set network.enableIDN boolean value to false

oh well - guess I ain't up on the unfixed exploits as much as I once was - figuring it was fixed already -- guess I was wrong...thanks for pointing that out Nem.

...so the Temporary workaround is what I've done above using about:config