| /external/chromium_org/third_party/WebKit/Source/core/page/ |
| D | Chrome.cpp | 51 Chrome::Chrome(Page* page, ChromeClient* client) in Chrome() function in blink::Chrome
58 Chrome::~Chrome() in ~Chrome()
62 PassOwnPtr<Chrome> Chrome::create(Page* page, ChromeClient* client) in create()
64 return adoptPtr(new Chrome(page, client)); in create()
67 void Chrome::invalidateContentsAndRootView(const IntRect& updateRect) in invalidateContentsAndRootView()
72 void Chrome::invalidateContentsForSlowScroll(const IntRect& updateRect) in invalidateContentsForSlowScroll()
77 IntRect Chrome::rootViewToScreen(const IntRect& rect) const in rootViewToScreen()
82 blink::WebScreenInfo Chrome::screenInfo() const in screenInfo()
87 void Chrome::contentsSizeChanged(LocalFrame* frame, const IntSize& size) const in contentsSizeChanged()
92 void Chrome::setWindowRect(const FloatRect& rect) const in setWindowRect()
[all …]
|
| D | Chrome.h | 55 class Chrome FINAL : public HostWindow {
57 virtual ~Chrome();
59 static PassOwnPtr<Chrome> create(Page*, ChromeClient*);
136 Chrome(Page*, ChromeClient*);
|
| /external/chromium_org/native_client_sdk/src/doc/sdk/ |
| D | examples.rst | 13 Your version of Chrome must be equal to or greater than the version of your SDK
15 must use Google Chrome version 35 or greater. To find out what version of Chrome
16 you're using, type ``about:chrome`` or ``about:version`` in the Chrome address
24 If you are using Chrome 31 or later, you can skip this section. To run Portable
25 Native Client applications you must specifically enable Native Client in Chrome:
27 #. Type ``about:flags`` in the Chrome address bar and scroll down to "Native
37 windows will restart when you relaunch Chrome.
153 Disable the Chrome cache
156 Chrome's intelligent caching caches resources aggressively. When building a
157 Native Client application you should disable the cache to make sure that Chrome
[all …]
|
| /external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/ |
| D | running.rst | 26 Running PNaCl applications from the open web is enabled in Chrome version 31 and
37 Native Client applications and the Chrome Web Store
43 Client applications must currently be distributed through the **Chrome Web
56 (extensions are typically used to extend the functionality of the Chrome
60 It's clearly not convenient to package and upload files to the Chrome Web Store
91 | Load your packaged application into Chrome as an | | |
103 | Load your hosted application into Chrome as an | | |
145 correct version of Chrome. Each version of Chrome supports a corresponding
146 version of the Pepper API. You (and your users) must use a version of Chrome
150 the application in Chrome 31 or higher. To check which version of Chrome you're
[all …]
|
| D | debugging.rst | 21 You can use Chrome's Task Manager to display information about a Native Client
36 A Native Client process appears with a Chrome extension icon (a jigsaw puzzle
71 JavaScript `console </devtools/docs/console-api>`_ in Chrome's Developer Tools.
89 By default stdout and stderr will appear in Chrome's stdout and stderr stream
113 ``NACLLOG`` variables to redirect output to a file, you must run Chrome with
121 to Chrome on startup::
126 The ``vmodule`` flag tells Chrome to log all calls to C Pepper interfaces that
128 and that your module calls). The ``enable-logging`` flag tells Chrome to log
178 with a matching Chrome version N. If the version of the debug bitcode pexe
179 does not match that of Chrome then the translation process may fail, and
[all …]
|
| /external/chromium_org/remoting/ |
| D | branding_Chrome | 3 DAEMON_FILE_NAME=Chrome Remote Desktop Host Service
4 IT2ME_HOST_DESCRIPTION=Remote Assistance Host for Chrome Remote Desktop
5 MAC_BUNDLE_ID=com.google.Chrome
9 MAC_HOST_PACKAGE_NAME=Chrome Remote Desktop Host
18 MAC_UNINSTALLER_NAME=Chrome Remote Desktop Host Uninstaller
19 ME2ME_HOST_DESCRIPTION=Chrome Remote Desktop Host
|
| /external/chromium_org/components/metrics/proto/ |
| D | chrome_user_metrics_extension.proto | 5 // Protocol buffer for Chrome UMA (User Metrics Analysis).
25 // Google Chrome product family.
28 // The product corresponding to this log. Note: The default value is Chrome,
29 // so Chrome products will not transmit this field.
34 // For Chrome clients, this id is unique to a top-level (one level above the
35 // "Default" directory) Chrome user data directory [1], and so is shared among
36 // all Chrome user profiles contained in this user data directory.
46 // relaunches Chrome.
|
| /external/chromium_org/google_apis/gcm/protocol/ |
| D | android_checkin.proto | 14 // Build characteristics unique to the Chrome browser, and Chrome OS
38 // The Chrome instance's version.
41 // The Channel (build type) of Chrome.
73 // For devices running MCS on Chrome, build-specific characteristics
75 // This will only be populated for Chrome builds/ChromeOS devices
92 // Chrome browser - Not Chrome OS. No hardware records.
95 // Chrome OS
|
| /external/chromium_org/remoting/host/installer/mac/uninstaller/ |
| D | remoting_uninstaller_app.mm | 34 NSLog(@"Chrome Remote Desktop uninstall starting.");
40 NSLog(@"Chrome Remote Desktop Host uninstall complete.");
46 message = @"Chrome Remote Desktop Host successfully uninstalled.";
48 message = @"Chrome Remote Desktop Host uninstall canceled.";
50 message = @"Chrome Remote Desktop Host uninstall authorization denied.";
64 @"Error! Unable to uninstall Chrome Remote Desktop Host.";
88 NSLog(@"Chrome Remote Desktop uninstall starting.");
95 NSLog(@"Chrome Remote Desktop Host uninstall complete.");
|
| /external/chromium_org/chrome/app_shim/ |
| D | app_mode_loader_mac.mm | 47 // ** 1: Get path to outer Chrome bundle.
53 // First check if Chrome exists at the last known location.
66 // TODO(jeremy): Display UI to allow user to manually locate the Chrome
72 // ** 2: Read the running Chrome version.
87 // If the version file does exist, it may have been left by a crashed Chrome
96 // ** 3: Read information from the Chrome bundle.
105 LOG(FATAL) << "Couldn't ready Chrome bundle info";
151 LOG(ERROR) << "Loading Chrome failed, launching Chrome with command line";
160 // Pass --app-shim-error to have Chrome rebuild this shim.
161 // If Chrome has rebuilt this shim once already, then rebuilding doesn't fix
[all …]
|
| /external/chromium_org/remoting/host/installer/linux/debian/ |
| D | chrome-remote-desktop.init | 73 log_begin_msg "Starting Chrome Remote Desktop host for $1..."
79 log_begin_msg "Stopping Chrome Remote Desktop host for $1..."
85 log_begin_msg "Reloading Chrome Remote Desktop host configuration for $1..."
91 log_begin_msg "Restarting Chrome Remote Desktop host for $1..."
|
| /external/chromium_org/tools/accessibility/nvda/ |
| D | README.txt | 1 This directory contains semi-automated tests of Chrome with
3 visually impaired users on Windows. It works by launching Chrome in a
6 processes other than a specific Chrome process ID. Each test automates
7 Chrome with a series of actions and asserts that NVDA gives the expected
14 Note - the version of Python installed by Chrome's depot_tools will not
42 4. Install Chrome Canary. The binary is typically installed in:
43 c:\Users\USERNAME\AppData\Local\Google\Chrome SxS\Application\chrome.exe
|
| /external/chromium_org/chrome/common/extensions/docs/server2/test_data/github_file_system/test_owner/repo/commits/ |
| D | HEAD | 112 …- \"name\": \"Google Wallet Server Validation Sample\",\n+ \"name\": \"Chrome In-App Payments Se…
124 …Chrome In App Payments API\n \n-You can use the Chrome In App Payments API (Chrome IAP API) to sel…
170 … \"App to test CWA.\",\n+ \"name\": \"Chrome In-App Payments Sample\",\n+ \"description\": \"App…
|
| /external/chromium_org/native_client_sdk/src/doc/devguide/ |
| D | distributing.rst | 14 `Chrome Web Store </webstore>`_ (CWS).
36 NaCl modules are only allowed for applications distributed through the `Chrome
43 through the Chrome Web Store apply to applications that contain NaCl modules as
50 * `Chrome extensions </extensions>`_
61 the Chrome Web Store. This file contains all of the application parts: A Chrome
79 multiple architectures (x86-64, x86-32, and ARM). Prior to Chrome 28, when users
83 Starting with Chrome 28, the Chrome Web Store includes a feature called
91 * The Chrome Web Store re-packages your app, so that users only download
138 earlier version of Chrome (prior to Chrome 28) that does not support
176 "description": "A reminder app that syncs across Chrome browsers.",
[all …]
|
| /external/chromium_org/build/ |
| D | chrome_settings.gypi | 15 ['branding=="Chrome"', {
16 'mac_bundle_id': 'com.google.Chrome',
19 'grit_defines': ['-D', 'mac_bundle_id=com.google.Chrome'],
20 }, { # else: branding!="Chrome"
|
| /external/webrtc/test/functional_test/ |
| D | README | 1 This test client is a simple functional test for WebRTC enabled Chrome build.
4 - A WebRTC Chrome binary.
15 2. Start the WebRTC Chrome build: $ <path_to_chome_binary>/chrome
17 <path_to_data> is where Chrome looks for all its states, use for example
27 2. Start the WebRTC Chrome build, see scenario (1).
29 4. On another machine, start the WebRTC Chrome build.
|
| /external/chromium_org/native_client_sdk/src/examples/tutorial/multi_platform/ |
| D | README | 10 This example shows how to use the SDK build system to generate a Chrome App
13 Starting with Chrome 28, the Chrome Web Store includes a feature called
21 * The Chrome Web Store re-packages your app, so that users only download
|
| /external/chromium_org/chrome/common/extensions/api/ |
| D | browser.idl | 5 // Use the <code>chrome.browser</code> API to interact with the Chrome browser
6 // associated with the current application and Chrome profile.
18 // application and Chrome profile. If no browser window for the Chrome
|
| /external/chromium_org/third_party/skia/tools/chromium/ |
| D | chrome_changes | 1 # This file contains references to Chrome CLs which are associated with Skia
2 # changes. If your Skia change requires a change in Chrome, add a line to this
3 # file which contains the codereview issue(s) for the Chrome change, eg:
|
| /external/skia/tools/chromium/ |
| D | chrome_changes | 1 # This file contains references to Chrome CLs which are associated with Skia
2 # changes. If your Skia change requires a change in Chrome, add a line to this
3 # file which contains the codereview issue(s) for the Chrome change, eg:
|
| /external/chromium_org/chrome/test/chromedriver/ |
| D | session_unittest.cc | 43 scoped_ptr<Chrome> chrome(new MockChrome()); in TEST()
51 scoped_ptr<Chrome> chrome(new MockChrome()); in TEST()
60 scoped_ptr<Chrome> chrome(new MockChrome()); in TEST()
86 scoped_ptr<Chrome> chrome(new MockChrome()); in TEST()
|
| /external/chromium_org/cloud_print/ |
| D | cloud_print_resources.gyp | 23 ['branding == "Chrome"', {
27 }, { # else branding!="Chrome"
60 ['branding == "Chrome"', {
64 }, { # else branding!="Chrome"
|
| /external/chromium_org/native_client_sdk/src/doc/devguide/tutorial/ |
| D | tutorial-part1.rst | 75 The SDK may consist of several "bundles", one per Chrome/Pepper version (see
90 Step 3: Set up the Chrome browser
93 PNaCl is enabled by default in Chrome version 31 and later. Please make sure
95 important to use a Chrome version that's the same or newer than the SDK bundle
101 To find out the version of Chrome, type ``about:chrome`` in the address bar.
104 Chrome cache. Chrome caches resources aggressively; disabling the cache helps
108 * Open Chrome's developer tools by clicking the menu icon |menu-icon| and
110 * Click the gear icon |gear-icon| in the bottom right corner of the Chrome
133 translator that is part of the Chrome browser.
167 :ref:`Step 2 <tutorial_step_2>`, you can now load the sample by pointing Chrome
[all …]
|
| /external/chromium_org/chrome/browser/mac/ |
| D | master_prefs.mm | 19 const char kMasterPreferencesFileName[] = "Google Chrome Master Preferences";
40 //~/Library/Application Support/Google/Chrome/Google Chrome Master Preferences
52 // On official builds, try /Library/Google/Google Chrome Master Preferences
|
| /external/chromium_org/chrome/common/extensions/docs/ |
| D | README | 11 Chrome source code. The server consumes these sources and generates the
19 * Docs are editable by anyone with Chrome commit access. This encourages
26 * Docs are branched automatically with Chrome's source code; the docs for each
27 Chrome release are kept with the corresponding source code.
29 * Users can always find the current doc for any Chrome release channel (i.e.,
31 with Chrome's release process.
70 5. Commit files as with any other Chrome change. The live server will update
|