Changes between Version 2 and Version 3 of Ticket #1801, comment 2


Ignore:
Timestamp:
01/21/2015 07:52:19 AM (6 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1801, comment 2

    v2 v3  
    1 This is because Chrome preserves the punycode encoding of domains, while Firefox seems to support IDN on the API level transparently decoding domains. In order to have the same behavior on Chrome as we have on Firefox, we would need to decode domains processed by Adblock Plus. 
    2  
    3 Therfore the `URI` class should be extended, to implicitly decode domains if they are encoded as punycode. And code processing URLs must be adapted to use that class. 
     1This is because Chrome preserves the punycode encoding of domains, while Firefox seems to support IDN on the API level transparently decoding domains. In order to have the same behavior on Chrome as we have on Firefox, we would need to decode domains processed by Adblock Plus. Therefore [https://developer.mozilla.org/en/docs/Web/API/URL URL objects] in combination with IDN-aware helper functions decoding the hostname.