summaryrefslogtreecommitdiffstats
path: root/chrome/common/security_style.h
diff options
context:
space:
mode:
authorerg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-01 18:17:23 +0000
committererg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-01 18:17:23 +0000
commit363680faae60b8ec1f6a57d3c701935a6f046fb6 (patch)
tree4530c2be35fbe1dfe384ffe03e8775993fa8f4fb /chrome/common/security_style.h
parent1693996df25b186a4523e9148fd8a5fe0405ccde (diff)
downloadchromium_src-363680faae60b8ec1f6a57d3c701935a6f046fb6.zip
chromium_src-363680faae60b8ec1f6a57d3c701935a6f046fb6.tar.gz
chromium_src-363680faae60b8ec1f6a57d3c701935a6f046fb6.tar.bz2
Refactor automation messages.
automation_messages used to live in chrome/test/automation, when it's needed by browser and chrome_frame. When I started lifting code out of headers and into implementation files, I was getting link errors and temporarily solved the problem by compiling the cc files manually into libbrowser.a. Now this is part of chrome/common/ which is included by all targets needed. While doing this, discover that automation IPC redefines the ContextMenuParams struct. Rename it to MiniContextMenuParams. BUG=51409 TEST=none Review URL: http://codereview.chromium.org/4200007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64637 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/security_style.h')
-rw-r--r--chrome/common/security_style.h35
1 files changed, 35 insertions, 0 deletions
diff --git a/chrome/common/security_style.h b/chrome/common/security_style.h
new file mode 100644
index 0000000..7d92d0e
--- /dev/null
+++ b/chrome/common/security_style.h
@@ -0,0 +1,35 @@
+// Copyright (c) 2006-2008 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_COMMON_SECURITY_STYLE_H_
+#define CHROME_COMMON_SECURITY_STYLE_H_
+#pragma once
+
+// Various aspects of the UI change their appearance according to the security
+// context in which they are displayed. For example, the location bar displays
+// a lock icon when it is displayed during a valid SSL connection.
+// SecuirtySyle enumerates these styles, but it is up to the UI elements to
+// adjust their display appropriately.
+enum SecurityStyle {
+ // SECURITY_STYLE_UNKNOWN indicates that we do not know the proper security
+ // style for this object.
+ SECURITY_STYLE_UNKNOWN,
+
+ // SECURITY_STYLE_UNAUTHENTICATED means the authenticity of this object can
+ // not be determined, either because it was retrieved using an unauthenticated
+ // protocol, such as HTTP or FTP, or it was retrieved using a protocol that
+ // supports authentication, such as HTTPS, but there were errors during
+ // transmission that render us uncertain to the object's authenticity.
+ SECURITY_STYLE_UNAUTHENTICATED,
+
+ // SECURITY_STYLE_AUTHENTICATION_BROKEN indicates that we tried to retrieve
+ // this object in an authenticated manner but were unable to do so.
+ SECURITY_STYLE_AUTHENTICATION_BROKEN,
+
+ // SECURITY_STYLE_AUTHENTICATED indicates that we successfully retrieved this
+ // object over an authenticated protocol, such as HTTPS.
+ SECURITY_STYLE_AUTHENTICATED,
+};
+
+#endif // CHROME_COMMON_SECURITY_STYLE_H_