When a Unicode hostname (e.g. a cyrillic one) is entered into chrome://settings/content, it is translated into punycode, and applied correctly on the target website.

However, there are ways to add a content settings which skip the punycode translation, such as changing content settings through the origin info bubble in Incognito. The setting is then not applied.

We need to ensure that content settings have no problem with Unicode hostnames, no matter how they were added; this can probably be solved by moving the punycode translation into HostContentSettingsMap setters.