Update StickyKeys overlay to show or hide AltGr depending on the

chrome/browser/chromeos/input_method/input_method_manager_impl.cc

Index: chrome/browser/chromeos/input_method/input_method_manager_impl.cc
diff --git a/chrome/browser/chromeos/input_method/input_method_manager_impl.cc b/chrome/browser/chromeos/input_method/input_method_manager_impl.cc
index 4a8912e0ac55e03febd05a3d24c8b3bd7738d633..174f01584a0f6eea2b371e51ac802e66d733b175 100644
--- a/chrome/browser/chromeos/input_method/input_method_manager_impl.cc
+++ b/chrome/browser/chromeos/input_method/input_method_manager_impl.cc
@@ -37,6 +37,53 @@ namespace {
 const char nacl_mozc_jp_id[] =
     "_comp_ime_fpfbhcjppmaeaijcidgiibchfbnhbeljnacl_mozc_jp";
 
+const char *kMod3LayoutIds[] = {
+  "xkb:de:neo:ger",
+  "xkb:ca:multix:fra",
+};
+
+const char *kAltGrLayoutIds[] = {
+  "xkb:be::fra",

[Seigo Nonaka, 2014/03/12 19:00:00]

Whoa! these xkb IDs are no longer available!(except for VPD settings)
They are gone and now extension wrapped IDs are used.
This is part of on screen keyboard support.

The new ID format is 
_comp_ime_ + fgoepimhcoialccpbmpnnblemnepkkao + <legacy ID>
So whitelist values should be like
_comp_ime_fgoepimhcoialccpbmpnnblemnepkkaoxkb:be::fra

BTW, I don't recommend comparing IME ID here. Please see comment in
IsMod3UsedByCurrentInputMethod 

+  "xkb:be::ger",
+  "xkb:be::nld",
+  "xkb:bg::bul",
+  "xkb:bg:phonetic:bul",
+  "xkb:br::por",
+  "xkb:ca::fra",
+  "xkb:ca:eng:eng",
+  "xkb:ca:multix:fra",
+  "xkb:ch::ger",
+  "xkb:ch:fr:fra",
+  "xkb:cz::cze",
+  "xkb:de::ger",
+  "xkb:de:neo:ger",
+  "xkb:dk::dan",
+  "xkb:ee::est",
+  "xkb:es::spa",
+  "xkb:es:cat:cat",
+  "xkb:fi::fin",
+  "xkb:fr::fra",
+  "xkb:gb:dvorak:eng",
+  "xkb:gb:extd:eng",
+  "xkb:gr::gre",
+  "xkb:hr::scr",
+  "xkb:il::heb",
+  "xkb:it::ita",
+  "xkb:latam::spa",
+  "xkb:lt::lit",
+  "xkb:no::nob",
+  "xkb:pl::pol",
+  "xkb:pt::por",
+  "xkb:ro::rum",
+  "xkb:se::swe",
+  "xkb:si::slv",
+  "xkb:sk::slo",
+  "xkb:tr::tur",
+  "xkb:ua::ukr",
+  "xkb:us:altgr-intl:eng",
+  "xkb:us:intl:eng",
+};
+
 bool Contains(const std::vector<std::string>& container,
               const std::string& value) {
   return std::find(container.begin(), container.end(), value) !=
@@ -715,6 +762,22 @@ InputMethodDescriptor InputMethodManagerImpl::GetCurrentInputMethod() const {
   return current_input_method_;
 }
 
+bool InputMethodManagerImpl::IsMod3UsedByCurrentInputMethod() const {
+  for (size_t i = 0; i < arraysize(kMod3LayoutIds); ++i) {
+    if (GetCurrentInputMethod().id() == kMod3LayoutIds[i])

[Seigo Nonaka, 2014/03/12 19:00:00]

Hmm, I don't think this works with third-party IME.
For example, if third-party IME uses us(intl) for their base keyboard layout,
this function will returns false since the third-party IME IDs are not known
until it is really installed.

I recommend you to move above whitelist to xkeyboad.cc and add new function into
IsMod3Available into XKeyboard.

BTW, I prefer ISOLevel5Shift rather than Mod3, because Mod3 sounds mask name
rather than key name to me.

+      return true;
+  }
+  return false;
+}
+
+bool InputMethodManagerImpl::IsAltGrUsedByCurrentInputMethod() const {
+  for (size_t i = 0; i < arraysize(kAltGrLayoutIds); ++i) {
+    if (GetCurrentInputMethod().id() == kAltGrLayoutIds[i])
+      return true;
+  }
+  return false;
+}
+
 XKeyboard* InputMethodManagerImpl::GetXKeyboard() {
   return xkeyboard_.get();
 }