summaryrefslogtreecommitdiffstats
path: root/chrome/chrome_tests.gypi
diff options
context:
space:
mode:
authorabarth@chromium.org <abarth@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-29 23:21:30 +0000
committerabarth@chromium.org <abarth@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-29 23:21:30 +0000
commit45dba2731166c1dfd7093b08afa22f73afc5f3c3 (patch)
tree353d3ea869d0c7521afe8a44d19e818c2744ca52 /chrome/chrome_tests.gypi
parent34ea9067e109e321d4418c80117bc667e6fba2cc (diff)
downloadchromium_src-45dba2731166c1dfd7093b08afa22f73afc5f3c3.zip
chromium_src-45dba2731166c1dfd7093b08afa22f73afc5f3c3.tar.gz
chromium_src-45dba2731166c1dfd7093b08afa22f73afc5f3c3.tar.bz2
Move latin1_string_conversions to base
Unfortunately, we can't keep this function in webkit/glue because not everyone who links in Blink depends on webkit/glue. For example, cc uses WebString but doesn't depend on webkit/glue. IMHO, the best solution to all these constraints is to put this function in base. It's concerned with concepts that make sense in base (strings and character sets). The only thing odd about the function is that it accepts Latin-1 or UTF-16, which is because of the underlying string representation in Blink. Review URL: https://chromiumcodereview.appspot.com/15732022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203003 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_tests.gypi')
0 files changed, 0 insertions, 0 deletions