Workaround for navigating by word in the omnibox on Windows.

ui/accessibility/BUILD.gn

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/linux/pkg_config.gni")
 import("//build/config/ui.gni")
 import("//build/json_schema_api.gni")
 import("//testing/test.gni")
 if (is_android) {
   import("//build/config/android/rules.gni")
@@ skipping 56 matching lines @@
     "platform/ax_platform_node_mac.mm",
     "platform/ax_platform_node_win.cc",
     "platform/ax_platform_node_win.h",
   ]
 
   defines = [ "ACCESSIBILITY_IMPLEMENTATION" ]
 
   public_deps = [
     ":ax_gen",
     "//base",
+    "//base_i18n",

[Mark Mentovai, 2016/03/09 18:42:35]

I don’t actually know if this is correct. I don’t know much about gn or our gn
build. This seems a little awkward because I thought that these were supposed to
be paths in the Chrome tree, and while we have base and ui at the root, we don’t
have base_i18n.

Based on
https://code.google.com/p/chromium/codesearch#search/&q=file:BUILD.gn%20//bas...,
I would expect to see this as //base:i18n

     "//ui/base",
     "//ui/gfx",
     "//ui/gfx/geometry",
   ]
 
   if (is_win) {
     public_deps += [ "//third_party/iaccessible2" ]
   }
 
   if (use_atk) {
@@ skipping 67 matching lines @@
 json_schema_api("ax_gen") {
   sources = [
     "ax_enums.idl",
   ]
   deps = [
     "//base/third_party/dynamic_annotations",
   ]
   root_namespace = "ui"
   schemas = true
 }