All IDN urls are currently displayed as Punycode by default. Whitelist of safe TLDs like Opera is needed to resolve this IDN problem more smartly. http://www.opera.com/windows/changelogs/800b2/ I suggest new pref like this: pref("network.IDN_TLDs_whitelist", "no, jp, de, se, kr, tw, cn, at, dk, ch, li"); If IDN url matches whitelist, the url should be displayed as Unicode whether "network.IDN_show_punycode" pref is true or false.

I don't think that this way is best. Because there is bug 283016. We cannot trust the sub-domain always. I think that better way is the way of Safari. Safari has blacklist of char. In this way we can trust all TLD and all sub-domain.

Safari has whitelist of char, not blacklist. http://docs.info.apple.com/article.html?artnum=301116-en

Sorry. I don't know it. I don't like the way of Safari too... Because on Safari, we cannot use inter-ideograph(Kanji).

whitelist of Opera 8.0 Beta 3 (Opera6.ini): IDNA White List=:no:jp:de:se:kr:tw:cn:at:dk:ch:li:museum:hu:

Should we create blacklist of char? # Is the way wrong for performance?

Isn't this a dup of bug 286534? (and bug 286535 for the char-blacklist)

Yes, this is a dupe. I'm just resolving it as a dupe of bug 286534 because that's what the summary line talks about. *** This bug has been marked as a duplicate of 286534 ***

Bug 286534 is about blacklist and different from Opera method. Solution of Bug 283016 may be bug 286535.

Opera 8.0 beta 3 allows the user to switch from a whitelist to a blacklist: http://www.opera.com/windows/changelogs/800b3/

(In reply to comment #8) > Bug 286534 is about blacklist and different from Opera method. I don't think so. See the summary line of that bug. It's about a generic method to dis/enable rendering IDNs with punycode depending on TLD.