MacViews: fix bubble direction in RTL.

tools/grit/grit_rule.gni

 # 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.
 
 # Instantiate grit. This will produce a script target to run grit, and a
 # static library that compiles the .cc files.
 #
 # Parameters
 #
 #   source (required)
@@ skipping 74 matching lines @@
 #     grit_flags = [ "-E", "foo=bar" ]  # Optional extra flags.
 #     # You can also put deps here if the grit source depends on generated
 #     # files.
 #   }
 import("//build/config/android/config.gni")
 import("//build/config/chrome_build.gni")
 import("//build/config/crypto.gni")
 import("//build/config/features.gni")
 import("//build/config/ui.gni")
 import("//third_party/closure_compiler/closure_args.gni")
+import("//ui/base/ui_features.gni")

[kjellander_webrtc, 2016/12/01 07:01:40]

I don't think it makes sense to have tools/grit depending on //ui in Chrome. Is
there another way to get around this?

In WebRTC, we're using the Chromium Android test framework and we pull in the
dependencies of it. With this change, our build broke since Chromium's ui/
directory is obviously not something we can have.
It broke our auto-roll here: https://codereview.webrtc.org/2542033002/

 
 assert(!enable_resource_whitelist_generation || is_android,
        "resource whitelist generation only works on android")
 
 declare_args() {
   # When set, this will fork out to grit at GN-time to get all inputs
   # referenced by the .grd file.
   #
   # Normal builds don't need this since proper incremental builds are handled
   # by grit writing out the inputs in .d files at build-time. But for analyze
@@ skipping 391 matching lines @@
     if (defined(invoker.configs)) {
       configs += invoker.configs
     }
 
     if (defined(invoker.visibility)) {
       visibility = invoker.visibility
     }
     output_name = grit_output_name
   }
 }