summaryrefslogtreecommitdiffstats
path: root/chrome/browser/global_keyboard_shortcuts_mac.h
diff options
context:
space:
mode:
authorcira@google.com <cira@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-10-15 20:27:04 +0000
committercira@google.com <cira@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-10-15 20:27:04 +0000
commit3cc4d00cae48dad31ac6bb2ed634c8ad5e098b37 (patch)
treed70c2b6368cc5478c5c835af8dd185d04e49dd96 /chrome/browser/global_keyboard_shortcuts_mac.h
parent048496265f826fc2e489a6319303e1122c3188a2 (diff)
downloadchromium_src-3cc4d00cae48dad31ac6bb2ed634c8ad5e098b37.zip
chromium_src-3cc4d00cae48dad31ac6bb2ed634c8ad5e098b37.tar.gz
chromium_src-3cc4d00cae48dad31ac6bb2ed634c8ad5e098b37.tar.bz2
Convert all exception patterns into punicode. Current matcher uses punicode entered in the omnibox and utf8 entered in the exception dialog, and they match only for ASCII urls.
This change will show punicode patterns to the user in the exception dialog. We already have that behavior if user uses Omnibox UI to specify the pattern. This CL doesn't solve the UI issue crbug.com/52629 as it still shows punycode representation of the pattern to the user. BUG=38317,52629 TEST=Open exception/images dialog, and add non-ascii pattern as an exception. Try going to that url. You should see the images on the page, and pattern you entered will be displayed as punicode in the exception dialog. Review URL: http://codereview.chromium.org/3087015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62784 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/global_keyboard_shortcuts_mac.h')
0 files changed, 0 insertions, 0 deletions