VR: Fix HTTP warning staying visible after exiting WebVR.

chrome/browser/android/vr_shell/ui_elements/ui_element_identifiers.h

Index: chrome/browser/android/vr_shell/ui_elements/ui_element_identifiers.h
diff --git a/chrome/browser/android/vr_shell/ui_elements/ui_element_identifiers.h b/chrome/browser/android/vr_shell/ui_elements/ui_element_identifiers.h
new file mode 100644
index 0000000000000000000000000000000000000000..c24d39502fa9dd7bad3823a78dedb098a4c5387a
--- /dev/null
+++ b/chrome/browser/android/vr_shell/ui_elements/ui_element_identifiers.h
@@ -0,0 +1,21 @@
+// Copyright 2017 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.
+
+#ifndef CHROME_BROWSER_ANDROID_VR_SHELL_UI_ELEMENTS_UI_ELEMENT_IDENTIFIERS_H_
+#define CHROME_BROWSER_ANDROID_VR_SHELL_UI_ELEMENTS_UI_ELEMENT_IDENTIFIERS_H_
+
+namespace vr_shell {
+
+// These identifiers may be used by UI elements to tag themselves for purposes
+// of testing or debugging.
+enum UiElementIdentifier {
+  kNone = 0,
+  kWebVrPermanentHttpSecurityWarning,
+  kWebVrTransientHttpSecurityWarning,

[Ian Vollick, 2017/05/19 14:42:32]

I love the idea of exposing ID's for testing, but perhaps a UiElement could have
a debug-only virtual property that returns a string? That'd keep the names
closer to the classes and might be nice for output.

[cjgrant, 2017/05/19 15:10:40]

Continued from previous comment...  As of now, that means a bunch of
conditionals in the scene manager and element classes.  As it is, it seems like
minimal overhead, and something we could use in production if we wanted to.

+  kCloseButton,
+};
+
+}  // namespace vr_shell
+
+#endif  // CHROME_BROWSER_ANDROID_VR_SHELL_UI_ELEMENTS_UI_ELEMENT_IDENTIFIERS_H_