File: whitelist.h

package info (click to toggle)
chromium-browser 57.0.2987.98-1~deb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 2,637,852 kB
  • ctags: 2,544,394
  • sloc: cpp: 12,815,961; ansic: 3,676,222; python: 1,147,112; asm: 526,608; java: 523,212; xml: 286,794; perl: 92,654; sh: 86,408; objc: 73,271; makefile: 27,698; cs: 18,487; yacc: 13,031; tcl: 12,957; pascal: 4,875; ml: 4,716; lex: 3,904; sql: 3,862; ruby: 1,982; lisp: 1,508; php: 1,368; exp: 404; awk: 325; csh: 117; jsp: 39; sed: 37
file content (46 lines) | stat: -rw-r--r-- 2,064 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
// Copyright 2015 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_EXTENSIONS_COMPONENT_EXTENSIONS_WHITELIST_WHITELIST_H_
#define CHROME_BROWSER_EXTENSIONS_COMPONENT_EXTENSIONS_WHITELIST_WHITELIST_H_

#include <string>

namespace extensions {

// =============================================================================
//
// ADDING NEW EXTENSIONS REQUIRES APPROVAL from chrome-eng-review@google.com
//
// The main acceptable use of extensions in the default Chrome experience (i.e.
// not installed explicitly by the user) are to implement things like the
// history or settings pages. These are things that look like web pages, load
// in response to explicit user action, and use no resources when not opened.
//
// If you are asking for approval to add a new built-in extension to Chrome
// (whether downloaded with the binary or downloaded later on-demand), check:
//
//  - It must not do anything on startup. Loading extensions processes on
//    startup can significantly slow things down.
//
//  - It must not have a background page. Extension processes use a nontrivial
//    amount of memory that makes them inappropriate for built-in features.
//
//  - Avoid event pages. Some events such as navigation will be even worse than
//    background pages since it will cause the extension to be frequently
//    loaded and unloaded. Even if your event page is "good" now, it's
//    something that is easy to regress with inocuous looking changes, so
//    try to use explicit C++ invocation of the extension when reasonable.
//
// =============================================================================

// Checks using an extension ID.
bool IsComponentExtensionWhitelisted(const std::string& extension_id);

// Checks using resource ID of manifest.
bool IsComponentExtensionWhitelisted(int manifest_resource_id);

}  // namespace extensions

#endif  // CHROME_BROWSER_EXTENSIONS_COMPONENT_EXTENSIONS_WHITELIST_WHITELIST_H_