{"issue":{"user":{"id":1240282,"login":"jsamuel","url":"https://api.github.com/users/jsamuel","avatar_url":"https://secure.gravatar.com/avatar/bc1d195cedb959a3946572b08ce9e7c7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bc1d195cedb959a3946572b08ce9e7c7"},"milestone":null,"title":"Link click is blocked if the link target contains IDN","created_at":"2011-12-22T03:54:38Z","labels":[{"name":"extension","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/labels/extension","color":"ededed"}],"updated_at":"2011-12-22T03:54:40Z","state":"open","id":2632891,"html_url":"https://github.com/RequestPolicy/requestpolicy/issues/48","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"For example, click <http://総務省.jp/>.\r\nRequestPolicy will block the request to xn--lhr645fjve.jp.\r\nI've found the following methods in nsIRequestPolicy broke the non-ascii chars.\r\n11\t  void registerHistoryRequest(in ACString destinationUri);\r\n12\t  void registerFormSubmitted(in ACString originUri, in ACString destinationUri);\r\n13\t  void registerLinkClicked(in ACString originUri, in ACString destinationUri);\r\nThe parameter type should be AString rather than ACString. ACString will cripple the non-ascii chars from JavaScript caller.\r\nIn general, XPCOM components written in JavaScript should use AString because JavaScript strings are encoded as UTF-16.","number":48,"url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/48","comments":1,"assignee":null},"comment":{"user":{"id":1240282,"login":"jsamuel","url":"https://api.github.com/users/jsamuel","avatar_url":"https://secure.gravatar.com/avatar/bc1d195cedb959a3946572b08ce9e7c7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bc1d195cedb959a3946572b08ce9e7c7"},"created_at":"2011-12-22T03:54:39Z","updated_at":"2011-12-22T03:54:39Z","id":3243749,"body":"[justin] Thanks for reporting this and finding the exact problems (and providing solutions). I've been very busy the past two months but will be working more on !RequestPolicy again now. I'm going to try to review these issues and the suggested fixes within the next few weeks.","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/comments/3243749"},"action":"created"}