Browser Support • The "network.IDN_show_punycode" setting in "about:config" ("prefs.js")

Moonchild wrote :
network.IDN_show_punycode (to true) -- Unnecessary because Pale Moon already shows punycode in the identity panel. Another downside would be not being able to enter IDN domain names in the address bar to navigate.

https://forum.palemoon.org/viewtopic.php?f=3&t=29674#p238462

My problem is that, even though I set "network.IDN_show_punycode = false", Pale Moon doesn't handle consistently all URLs that have unicode characters in "host".
Examples:
***

Why is this a problem for me? When I added the option to search with unicode characters in "Intercept & Modify HTTP Response 4.3" add-on, I added this option for "host" as well (not just for "path"). In the tests I did back then, Pale Moon did not convert unicode HOSTs to "punycode" HOSTs, and so the filters worked fine. Now I came (accidentally) across the URL with Japanese characters above, where the HOST is converted by Pale Moon to "punycode" HOST. Because of this, the filters with unicode characters in HOST no longer work for this page. In such cases, users of the add-on would have to use filters that use "punycode" HOSTs, and so there is no longer a generally valid rule for creating filters.

I would appreciate your answers to the following questions:

1. Why doesn't Pale Moon treat all URLs with unicode characters in HOST the same when using the "network.IDN_show_punycode = false" setting?

2. Is there another setting in Pale Moon to stop it converting any HOST to "punycode" when "network.IDN_show_punycode = false"?

---