Archive

Archive for February 22, 2012

HP Gas Distributor in HYD

February 22, 2012 Leave a comment

Malkajgiri:

SECUNDERABAD GAS COMPANY

26-81 EXCEL KRISHNA, SAFILGUDA STATION ROAD, CHANAKYAPURI COLONY, MALKAJGIRI , SECUNDERABAD 500 047SAFILGUDA, Dist. HYDERABAD, ANDHRA PRADESH – 500047
Email : secunderabad.hyderabad@hpgas.hpcl.co.in
Phone : (40) 27244144 27244133

 

Somajiguda:

HINDUSTAN GAS COMPANY

6-3-904/12/A JAFFAR ALI BAGH, SOMAJIGUDAHYDERABAD, Dist. HYDERABAD, ANDHRA PRADESH – 500003
Email : hindustan.hyderabad@hpgas.hpcl.co.in
Phone : (040) 23312858 23328724

About these ads
Categories: Self Management

Fix: Microsoft Office 2010 Outlook 2010 Mouse Cursor/Pointer Display Issue in XenApp Session

February 22, 2012 Leave a comment

Scenario:

When you setup Outlook 2010 in Citrix XenApp Server Desktop session and you launch the application for the first time within the session as end user.  You configure the Outlook to use the ‘No email support’ and use the ‘recommended settings’.  You notice that your mouse Cursor/Pointer Display doesn’t appear in Outlook application though it just works fine for other applications in the same server desktop session.

 

Fix:

Have the Outlook launched as the end user at least once in a full desktop (RDP or runas) locally on the server. So that Outlook will have all of the files updated and refreshed on the serve in order for proper rendering. Then launch the same desktop session and you’ll have the Cursor displaying fine for Outlook.

Categories: Citrix, MS-Office, Repackaging

Google Chrome: Your profile could not be opened correctly.

February 22, 2012 7 comments

Error:

—————————

Google Chrome

—————————

Your profile could not be opened correctly.

Some features may be unavailable. Please check that the profile exists and you have permission to read and write its contents.

—————————

OK

—————————

 

image

 

Fix: This can happen if the Chrome is unable to spawn it’s default tab chrome sub-process which actually load the user profile.

Most possible that you are launching the chrome from a thin session clients like XenApp which doesn’t support Chrome to load fully.  In case you are using XenApp, you need to conver your app into Server Desktop so that  it runs in full windows shell.

Categories: Browsers

Scripting Automation of Chrome Actions

February 22, 2012 Leave a comment

Chrome Setup:

The default browser based install of the Chrome installs browser for that user only.  To have chrome installed for all users and be able to manage it, you have to install a standalone version of Chrome browser that installs for all users on a system.

 

Browser based install places chrome in:

C:\Users\<username>\AppData\Local\Google\Chrome\Application\chrome.exe

Standalone installer places chrome in:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

 

Scripting Automation:

To start Chrome with launch/load of a website automatically:

  1. Start chrome exe with URL, examples below:
    1. "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" www.microsoft.com
    2. "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" http://www.microsoft.com/en-us/default.aspx
    3. "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" http://testserver/mysite/logon.aspx
  2. launch the shortcut with the URL as parameter to the target executable as shown below:
    1. Shortcut target: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" http://localhost/myapp/

 

    Automatically sending keyboard/mouse keys/clicks to chromes pages: 
  1. Activating the Chrome browser window or setting Chrome as active window
    1. shell.appactivate("<URL name> – Google Chrome")
  2. Currently Chrome has bugs sending automated keys
Categories: Browsers, Programming

CTX127897 – Cannot Use the Mouse on Seamless Applications on XenApp 6 – Citrix Knowledge Center

February 22, 2012 Leave a comment

Symptoms

From some Windows XP machines using online plug-in 11.2, you cannot use the mouse properly in a Seamless Application on XenApp 6.

The mouse pointer will be about two inches to the right when you click.

The issue does not occur in a fixed Window.

If you use the Shift+F2 key combination to change from Seamless to a Fixed Window, the application screen starts flickering and does not stop until you close the application.

Resolution

Upgrade to Online Plug-in 12.1 to solve the issue.

This document applies to:

Source: CTX127897 – Cannot Use the Mouse on Seamless Applications on XenApp 6 – Citrix Knowledge Center

Categories: Citrix

List of Chromium Command Line Switches

February 22, 2012 Leave a comment

List of Chromium Command Line Switches

There are lots of command lines which can be used with the Chromium browser. Some change behavior of features, others are for debugging or experimenting. This page lists the available switches including their conditions and descriptions. Last automated update occurred on 2012-02-21.

Condition

Explanation

–0

prohibited: never inline matches

–1

The values the kOmniboxInlineHistoryQuickProvider switch may have, as in "–omnibox-inline-history-quick-provider-allowed=1" allowed: if HistoryQuickProvider thinks it appropriate, it can inline ( == current behavior as of 2/2012).

–allow-cross-origin-auth-prompt

Allow third party content included on a page to prompt for a HTTP basic auth username/password pair.

–allow-file-access

On ChromeOS, file:// access is disabled except for certain whitelisted directories. This switch re-enables file:// for testing.

–allow-file-access-from-files

By default, file:// URIs cannot read other file:// URIs. This is an override for developers who need the old behavior for testing.

–allow-http-background-page

Allow non-https URL for background_page for hosted apps.

–allow-nacl-socket-api

Specifies comma-separated list of extension ids to grant access to TCP/UDP socket APIs.

–allow-outdated-plugins

Don’t block outdated plugins.

–allow-running-insecure-content

By default, an https page cannot run JavaScript, CSS or plug-ins from http URLs. This provides an override to get the old insecure behavior.

–allow-sandbox-debugging

Allows debugging of sandboxed processes (see zygote_main_linux.cc).

–allow-scripting-gallery

Allows injecting extensions and user scripts on the extensions gallery site. Normally prevented for security reasons, but can be useful for automation testing of the gallery.

–allow-webui-compositing

Allow compositing on chrome:// pages.

–alsa-input-device[1]

The Alsa device to use when opening an audio input stream.

–alsa-output-device[1]

The Alsa device to use when opening an audio stream.

–always-authorize-plugins

This prevents Chrome from requiring authorization to run certain widely installed but less commonly used plug-ins.

–app

Specifies that the associated value should be launched in "application" mode.

–app-id

Specifies that the extension-app with the specified id should be launched according to its configuration.

–app-notify-channel-server-url

A URL for the server which assigns channel ids for server pushed app notifications.

–apple

No description

–apps-checkout-url

Override the apps checkout URL, which is used to determine when to expose some private APIs.

–apps-gallery-download-url

The URL that the webstore APIs download extensions from. Note: the URL must contain one ‘%s’ for the extension ID.

–apps-gallery-install-auto-confirm-for-tests

A setting to cause extension/app installs from the webstore skip the normal confirmation dialog. A value of ‘accept’ means to always act as if the dialog was accepted, and ‘cancel’ means to always act as if the dialog was cancelled.

–apps-gallery-return-tokens

Specifying this flag allows the webstorePrivate APIs to return browser (aka sync) login tokens to be used for auto-login in the Web Store (normally they do not).

–apps-gallery-update-url

The update url used by gallery/webstore extensions.

–apps-gallery-url

The URL to use for the gallery link in the app launcher.

–apps-new-install-bubble

Whether to always use the new app install bubble when installing an app.

–apps-no-throb

Disable throbber for extension apps.

–assert-test

Causes the browser process to throw an assertion on startup.

–auth-ext-path[2]

Enables overriding the path for the default authentication extension.

–auth-negotiate-delegate-whitelist

Whitelist of servers that Negotiate will generate delegated Kerberos tickets for.

–auth-schemes

HTTP authentication schemes to enable. This is a comma separated list of authentication schemes (basic, digest, ntlm, and negotiate). By default all schemes are enabled. The primary use of this command line flag is to help triage autentication-related issues reported by end-users.

–auth-server-whitelist

Whitelist of servers which NTLM and Negotiate can automatically authenticate with using the default credentials of the currently logged in user.

–auto

These are the values the switch may have, as in "–prerender=auto". auto: Allow field trial selection in both prerender and prefetch.

–auto-launch-at-startup

A flag that is used to tell Chrome that it was launched automatically at computer startup and not by some user action.

–automation-channel

The value of this switch tells the app to listen for and broadcast automation-related messages on IPC channel with the given ID.

–automation-reinitialize-on-channel-error

Causes the automation provider to reinitialize its IPC channel instead of shutting down when a client disconnects.

–blacklist-accelerated-compositing

Blacklist the GPU for accelerated compositing.

–blacklist-webgl

Blacklist the GPU for WebGL.

–browser-subprocess-path

Path to the exe to run for the renderer and plugin subprocesses.

–bwsi[3]

Indicates that the browser is in "browse without sign-in" (Guest session) mode. Should completely disable extensions, sync and bookmarks.

–channel

The value of this switch tells the child process which IPC channel the browser expects to use to communicate with it.

–check-cloud-print-connector-policy

Checks the cloud print connector policy, informing the service process if the policy is set to disallow the connector, then quits.

–check-for-update-interval

How often (in seconds) to check for updates. Should only be used for testing purposes.

–chrome-frame

Run Chrome in Chrome Frame mode. This means that Chrome expects to be run as a dependent process of the Chrome Frame plugin.

–chrome-version

Tells chrome to load the specified version of chrome.dll on Windows. If this version cannot be loaded, Chrome will exit.

–cipher-suite-blacklist

Comma-separated list of SSL cipher suites to disable.

–clear-token-service[2]

Clear the token service before using it. This allows simulating the expiration of credentials during testing.

–cloud-print-delete-file

Used with kCloudPrintFile. Tells Chrome to delete the file when finished displaying the print dialog.

–cloud-print-file

Tells chrome to display the cloud print dialog and upload the specified file for printing.

–cloud-print-file-type

Specifies the mime type to be used when uploading data from the file referenced by cloud-print-file. Defaults to "application/pdf" if unspecified.

–cloud-print-job-title

Used with kCloudPrintFile to specify a title for the resulting print job.

–cloud-print-print-ticket

Used with kCloudPrintFile to specify a JSON print ticket for the resulting print job. Defaults to null if unspecified.

–cloud-print-proxy-id

The unique id to be used for this cloud print proxy instance.

–cloud-print-service

The URL of the cloud print service to use, overrides any value stored in preferences, and the default. Only used if the cloud print service has been enabled (see enable-cloud-print).

–component-updater-debug

Comma-separated options to troubleshoot the component updater. Only valid for the browser process.

–compress-sys-feedback[3]

Flag to trigger ChromeOS system log compression during feedback submit.

–conflicting-modules-check

Causes the browser process to inspect loaded and registered DLLs for known conflicts and warn the user.

–country

The Country we should use. This is normally obtained from the operating system during first run and cached in the preferences afterwards. This is a string value, the 2 letter code from ISO 3166-1.

–crash-on-hang-seconds

Causes the browser process to crash if browser threads are not responding for the given number of seconds.

–crash-on-hang-threads

Comma separated list of BrowserThreads that cause browser process to crash if the given browser thread is not responsive. UI,IO,DB,FILE,CACHE are the list of BrowserThreads that are supported. For example: –crash-on-hang-threads=UI,IO –> Crash the browser if UI or IO thread is not responsive.

–crash-on-live

Causes the browser process to crash if the number of browser threads that are responding is equal to the given number. For example: –crash-on-live=1 –> Crash if only one thread is responsive and all other threads are not responsive.

–crash-test

Causes the browser process to crash on startup.

–create-mobile-bookmarks-folder

If true the mobile bookmarks folder is created on the sync side.

–debug-children

Will add kDebugOnStart to every child processes. If a value is passed, it will be used as a filter to determine if the child process should have the kDebugOnStart flag passed on or not.

–debug-devtools-frontend

Path to the inspector files on disk (allows reloading of devtool files without having to restart the browser).

–debug-enable-frame-toggle

Enables a frame context menu item that toggles the frame in and out of glass mode (Windows Vista and up only).

–debug-on-start

If the program includes base/debug/debug_on_start_win.h, the process will (on Windows only) start the JIT system-registered debugger on itself and will wait for 60 seconds for the debugger to attach to itself. Then a break point will be hit.

–debug-plugin-loading

Dumps extra logging about plugin loading to the log file.

–debug-print

Enables support to debug printing subsystem.

–debug-views-paint[4]

Enables debug paint in views framework. Enabling this causes the damaged region being painted to flash in red.

–desktop

No description

–device-management-url

Specifies the URL at which to fetch configuration policy from the device management backend. Specifying this switch turns on managed policy from the device management backend.

–diagnostics

Triggers a pletora of diagnostic modes.

–disable-3d-apis

Disables client-visible 3D APIs, in particular WebGL and Pepper 3D. This is controlled by policy and is kept separate from the other enable/disable switches to avoid accidentally regressing the policy support for controlling access to these APIs.

–disable-accelerated-2d-canvas

Disable gpu-accelerated 2d canvas.

–disable-accelerated-compositing

Disables accelerated compositing.

–disable-accelerated-layers

Disables the hardware acceleration of 3D CSS and animation.

–disable-accelerated-plugins

Disables the hardware acceleration of plugins.

–disable-accelerated-video

Disables GPU accelerated video display.

–disable-application-cache

Disable the ApplicationCache.

–disable-audio

Replaces the audio IPC layer for <audio> and <video> with a mock audio device, useful when using remote desktop or machines without sound cards. This is temporary until we fix the underlying problem. TODO(scherkus): remove –disable-audio when we have a proper fallback mechanism.

–disable-auth-negotiate-cname-lookup

Disable CNAME lookup of the host when generating the Kerberos SPN for a Negotiate challenge. See HttpAuthHandlerNegotiate::CreateSPN for more background.

–disable-background-mode

Disable background mode (background apps will not keep chrome running in the background).

–disable-background-networking

Disable several subsystems which run network requests in the background. This is for use when doing network performance testing to avoid noise in the measurements.

–disable-backing-store-limit

Disable limits on the number of backing stores. Can prevent blinking for users with many windows/tabs and lots of memory.

–disable-breakpad

Disables the crash reporting.

–disable-client-side-phishing-detection

This switch is used to disable the client-side phishing detection feature. Note that even if client-side phishing detection is enabled, it will only be active if the user has opted in to UMA stats and SafeBrowsing is enabled in the preferences.

–disable-composited-core-animation-plugins[5]

No description

–disable-connect-backup-jobs

Disables establishing a backup TCP connection if a specified timeout is exceeded.

–disable-crl-sets

Disables establishing certificate revocation information by downloading a set of CRLs rather than performing on-line checks.

–disable-custom-jumplist

Disables the custom JumpList on Windows 7.

–disable-custom-protocol-os-check

Disables checking whether custom protocol handlers are registered with the OS and removing those that are not. This is used during automated testing.

–disable-data-transfer-items

Disables data transfer items.

–disable-databases

Disables HTML5 DB support.

–disable-default-apps

Disables installation of default apps on first run. This is used during automated testing.

–disable-desktop-notifications

Disables desktop notifications (default enabled on windows).

–disable-desktop-shortcuts[6]

Disables profile desktop shortcuts handling, preventing their creation, modification or removal.

–disable-device-orientation

Disables device orientation events.

–disable-dhcp-wpad

Disables retrieval of PAC URLs from DHCP as per the WPAD standard.

–disable-extensions

Disable extensions.

–disable-extensions-file-access-check

Disable checking for user opt-in for extensions that want to inject script into file URLs (ie, always allow it). This is used during automated testing.

–disable-extensions-resource-whitelist

Disable mandatory enforcement of web_accessible_resources in extensions.

–disable-file-system

Disable FileSystem API.

–disable-flash-sandbox

Disables the sandbox for the built-in flash player.

–disable-fullscreen

Enable the JavaScript Full Screen API.

–disable-geolocation

Suppresses support for the Geolocation javascript API.

–disable-gl-multisampling

Disable GL multisampling.

–disable-glsl-translator

Disable the GLSL translator.

–disable-gpu-driver-bug-workarounds

Disable workarounds for various GPU driver bugs.

–disable-gpu-sandbox

Disable the GPU process sandbox.

–disable-gpu-vsync

Stop the GPU from synchronizing on the vsync before presenting.

–disable-gpu-watchdog

Disable the thread that crashes the GPU process if it stops responding to messages.

–disable-hang-monitor

Suppresses hang monitor dialogs in renderer processes. This may allow slow unload handlers on a page to prevent the tab from closing, but the Task Manager can be used to terminate the offending process in this case.

–disable-history-quick-provider

Disable the use of the HistoryQuickProvider for autocomplete results.

–disable-history-url-provider

Disable the use of the HistoryURLProvider for autocomplete results.

–disable-image-transport-surface

Disable the use of an ImageTransportSurface. This means the GPU process will present the rendered page rather than the browser process.

–disable-improved-download-protection

Disables improved SafeBrowsing download protection.

–disable-interactive-form-validation

Disables HTML5 Forms interactive validation.

–disable-internal-flash

Disable the internal Flash Player.

–disable-ip-pooling

Disables IP Pooling within the networks stack (SPDY only). When a connection is needed for a domain which shares an IP with an existing connection, attempt to use the existing connection.

–disable-ipv6

Don’t resolve hostnames to IPv6 addresses. This can be used when debugging issues relating to IPv6, but shouldn’t otherwise be needed. Be sure to file bugs if something isn’t working properly in the presence of IPv6. This flag can be overidden by the "enable-ipv6" flag.

–disable-java

Prevent Java from running.

–disable-javascript

Don’t execute JavaScript (browser JS like the new tab page still runs).

–disable-javascript-i18n-api

Disable JavaScript I18N API.

–disable-local-storage

Disable LocalStorage.

–disable-logging

Force logging to be disabled. Logging is enabled by default in debug builds.

–disable-pepper-3d-for-untrusted-use

Disables NativeClient’s access to Pepper3D.

–disable-plugins

Prevent plugins from running.

–disable-popup-blocking

Disable pop-up blocking.

–disable-preconnect

Disable speculative TCP/IP preconnection.

–disable-print-preview[7]

Disable print preview (Not exposed via about:flags. Only used for testing.)

–disable-prompt-on-repost

Normally when the user attempts to navigate to a page that was the result of a post we prompt to make sure they want to. This switch may be used to disable that check. This switch is used during automated testing.

–disable-remote-fonts

Disable remote web font support. SVG font should always work whether this option is specified or not.

–disable-renderer-accessibility

Turns off the accessibility in the renderer.

–disable-restore-background-contents

Prevents the URLs of BackgroundContents from being remembered and re-launched when the browser restarts.

–disable-seccomp-sandbox

Disable the seccomp sandbox (Linux only)

–disable-session-storage

Disable session storage.

–disable-shared-workers

Enable shared workers. Functionality not yet complete.

–disable-shortcuts-provider

Disables the ShortcutsProvider for autocomplete results.

–disable-site-specific-quirks

Disable site-specific tailoring to compatibility issues in WebKit.

–disable-smooth-scrolling

Disable smooth scrolling for testing.

–disable-software-rasterizer

Disables the use of a 3D software rasterizer.

–disable-speech-input

Disables speech input.

–disable-ssl-false-start

Disable False Start in SSL and TLS connections.

–disable-ssl3

Disable SSL v3 (usually for testing purposes).

–disable-sync

Disable syncing browser data to a Google Account.

–disable-sync-app-notifications

Disable syncing app notifications.

–disable-sync-apps

Disable syncing of apps.

–disable-sync-autofill

Disable syncing of autofill.

–disable-sync-autofill-profile

Disable syncing of autofill Profile.

–disable-sync-bookmarks

Disable syncing of bookmarks.

–disable-sync-encryption

Disable sync encryption options.

–disable-sync-extensions

Disable syncing of extensions.

–disable-sync-passwords[8]

Disable syncing browser passwords.

–disable-sync-preferences

Disable syncing of preferences.

–disable-sync-search-engines

Disable syncing custom search engines.

–disable-sync-themes

Disable syncing of themes.

–disable-sync-typed-urls

Disable syncing browser typed urls.

–disable-tab-closeable-state-watcher

TabCloseableStateWatcher disallows closing of tabs and browsers under certain situations on ChromeOS. Some tests expect tabs or browsers to close, so we need a switch to disable the watcher.

–disable-tls1

Disable TLS v1.0 (usually for testing purposes).

–disable-translate

Allow disabling of translate from the command line to assist with automated browser testing (e.g. Selenium/WebDriver). Normal browser users should disable translate with the preference.

–disable-uber-page

Disable uber page command and URL redirection.

–disable-web-intents

Enable Web Intents.

–disable-web-resources

Enables the backend service for web resources, used in the new tab page for loading tips and recommendations from a JSON feed.

–disable-web-security

Don’t enforce the same-origin policy. (Used by people testing their sites.)

–disable-web-sockets

Disable Web Sockets support.

–disable-webaudio

Disable web audio API.

–disable-webgl

Disable experimental WebGL support.

–disable-winsta

Disables the alternate window station for the renderer.

–disable-xss-auditor

Disable WebKit’s XSSAuditor. The XSSAuditor mitigates reflective XSS.

–disabled

disabled: No prerendering or prefetching.

–disk-cache-dir

Use a specific disk cache location, rather than one derived from the UserDatadir.

–disk-cache-size

Forces the maximum disk space to be used by the disk cache, in bytes.

–dns-log-details

No description

–dns-prefetch-disable

Disables prefetching of DNS information.

–dns-server

Use the specified DNS server for raw DNS resolution.

–dom-automation

Specifies if the dom_automation_controller_ needs to be bound in the renderer. This binding happens on per-frame basis and hence can potentially be a performance bottleneck. One should only enable it when automating dom based tests.

–downloads-new-ui

Replaces the download shelf with a new experimental UI.

–dump-histograms-on-exit

Dump any accumualted histograms to the log when browser terminates (requires logging to be enabled to really do anything). Used by developers and test scripts.

–dump-profile-graph[2]

Dumps dependency information about our profile services into a dot file in the profile directory.

–egl

No description

–enable-accelerated-2d-canvas

Enable gpu-accelerated 2d canvas.

–enable-accelerated-filters

Enable gpu-accelerated SVG/W3C filters.

–enable-accelerated-painting

Enable hardware accelerated page painting.

–enable-accessibility

Enables WebKit accessibility within the renderer process.

–enable-accessibility-logging

Turns on extremely verbose logging of accessibility events.

–enable-aero-peek-tabs

Enables AeroPeek for each tab. (This switch only works on Windows 7).

–enable-asynchronous-spellchecking

Enables asynchronous spellchecking features for all time. Enabling this feature also enables unified spellchecking.

–enable-auth-negotiate-port

Enable the inclusion of non-standard ports when generating the Kerberos SPN in response to a Negotiate challenge. See HttpAuthHandlerNegotiate::CreateSPN for more background.

–enable-autofill-feedback

With this flag set, Chrome will occasionally prompt the user to volunteer Autofill usage data beyond what is collected by default. This is data that we expect to be helpful for debugging, but that we do not want to send up automatically due to privacy concerns.

–enable-autologin

Enables the pre- and auto-login features. When a user signs in to sync, the browser’s cookie jar is pre-filled with GAIA cookies. When the user visits a GAIA login page, an info bar can help the user login.

–enable-benchmarking

Enables the benchmarking extensions.

–enable-bluetooth[3]

Enables bluetooth support on ChromeOS

–enable-bundled-ppapi-flash

Enables the bundled PPAPI version of Flash.

–enable-cloud-print-proxy

This applies only when the process type is "service". Enables the Cloud Print Proxy component within the service process.

–enable-composite-to-texture

Enables compositing to texture instead of display.

–enable-connect-backup-jobs

Enables establishing a backup TCP connection if a specified timeout is exceeded.

–enable-crash-reporter[9]

A flag, generated internally by Chrome for renderer and other helper process command lines on Linux and Mac. It tells the helper process to enable crash dumping and reporting, because helpers cannot access the profile or other files needed to make this decision.

–enable-crxless-web-apps

Enables web developers to create apps for Chrome without using crx packages.

–enable-dcheck

Enable DCHECKs in release mode.

–enable-deferred-2d-canvas

Enable deferred 2d canvas rendering.

–enable-device-motion

Enables device motion events.

–enable-device-policy[3]

Enables device policy support on ChromeOS.

–enable-devtools-experiments

If true devtools experimental settings are enabled.

–enable-experimental-extension-apis

Enables extension APIs that are in development.

–enable-expose-for-tabs[5]

Enables the tabs expose feature ( http://crbug.com/50307 ).

–enable-extension-activity-logging

Enables logging for extension activity.

–enable-extension-activity-ui

Enables the extension activity UI.

–enable-extension-timeline-api

Enable experimental timeline API.

–enable-fastback

Enable the fastback page cache.

–enable-file-cookies

By default, cookies are not allowed on file://. They are needed for testing, for example page cycler and layout tests. See bug 1157243.

–enable-fixed-position-compositing

Enables the creation of compositing layers for fixed position elements.

–enable-gamepad

Enable the Gamepad API

–enable-gpu-client-logging

No description

–enable-gpu-service-logging

Turns on GPU logging (debug build only).

–enable-gview[3]

Enable the redirection of viewable document requests to the Google Document Viewer.

–enable-handle-auditing[6]

Enumerates and prints a child process’ most dangerous handles when it is terminated.

–enable-handle-auditing-all[6]

The same as kAuditHandles except all handles are enumerated.

–enable-http-pipelining

Enable HTTP pipelining. Attempt to pipeline HTTP connections. Heuristics will try to figure out if pipelining can be used for a given host and request. Without this flag, pipelining will never be used.

–enable-in-browser-thumbnailing

Enable the in-browser thumbnailing, which is more efficient than the in-renderer thumbnailing, as we can use more information to determine if we need to update thumbnails.

–enable-ip-pooling

Enables IP Pooling within the networks stack (SPDY only). When a connection is needed for a domain which shares an IP with an existing connection, attempt to use the existing connection.

–enable-ipc-fuzzing

/ Enable the IPC fuzzer for reliability testing

–enable-ipv6

Enable IPv6 support, even if probes suggest that it may not be fully supported. Some probes may require internet connections, and this flag will allow support independent of application testing. This flag overrides "disable-ipv6" which appears elswhere in this file.

–enable-logging

Force logging to be enabled. Logging is disabled by default in release builds.

–enable-mac-cookies

Enables MAC cookies in the network stack. These cookies use HMAC to protect session state from passive network attackers. http://tools.ietf.org/html/draft-hammer-oauth-v2-mac-token

–enable-media-source

Enables Media Source API on <audio>/<video> elements.

–enable-media-stream

Enable media stream in WebKit. http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#mediastream

–enable-memory-info

Allows reporting memory info (JS heap size) to page.

–enable-mobile-dialog[3]

Enables mobile setup in a dialog.

–enable-monitor-profile

On Windows, converts the page to the currently-installed monitor profile. This does NOT enable color management for images. The source is still assumed to be sRGB.

–enable-nacl

Runs the Native Client inside the renderer process and enables GPU plugin (internally adds lEnableGpuPlugin to the command line).

–enable-nacl-debug

Enables debugging via RSP over a socket.

–enable-nacl-exception-handling

Enables hardware exception handling via debugger process.

–enable-onc-policy[3]

Enables support for policy-configured networks.

–enable-origin-bound-certs

Enables TLS origin bound certificate extension.

–enable-panels

Enables panels (always on-top docked pop-up windows).

–enable-partial-swap

Enables partial swaps in the WK compositor on platforms that support it.

–enable-pepper-testing

Enables the testing interface for PPAPI.

–enable-per-tile-painting

Enable per-tile page painting.

–enable-platform-apps

Enables advanced app capabilities.

–enable-pnacl

Enables the installation and usage of Portable Native Client.

–enable-pointer-lock

Enable the JavaScript Pointer Lock API.

–enable-preparsed-js-caching

Enable caching of pre-parsed JS script data. See http://crbug.com/32407.

–enable-print-preview

Enable print preview (work in progress).

–enable-privileged-webgl-extensions

Enable privileged WebGL extensions; without this switch such extensions are available only to Chrome extensions.

–enable-profiling

Enables tracking of tasks in profiler for viewing via about:profiler. To predominantly disable tracking (profiling), use the command line switch: –enable-profiling=0 Some tracking will still take place at startup, but it will be turned off during chrome_browser_main.

–enable-resource-content-settings

Enable content settings based on host *and* plug-in.

–enable-restore-session-state

Experimental. Enables restoring session state (cookies, session storage, etc.) when autorestarting.

–enable-sandbox-logging

Cause the OS X sandbox write to syslog every time an access to a resource is denied by the sandbox.

–enable-sdch

Enable support for SDCH filtering (dictionary based expansion of content). Optional argument is *the* only domain name that will have SDCH suppport. Default is "-enable-sdch" to advertise SDCH on all domains. Sample usage with argument: "-enable-sdch=.google.com" SDCH is currently only supported server-side for searches on google.com.

–enable-seccomp-sandbox

Enable the seccomp sandbox (Linux only)

–enable-sensors[3]

Rotate the screen in response to orientation changed events from dbus. Will be reused for more generic sensors.

–enable-shadow-dom

Enable shadow DOM API

–enable-smooth-scrolling

On platforms that support it, enable smooth scroll animation.

–enable-ssl-cached-info

Enables TLS cached info extension.

–enable-static-ip-config[3]

Enables static ip configuration. This flag should be removed when it’s on by default.

–enable-stats-table

Enables StatsTable, logging statistics to a global named shared memory table.

–enable-strict-site-isolation

Experimentally ensure each renderer process has pages from only one site. This is expected to break compatibility with many pages for now.

–enable-sync-extension-settings

Enable syncing extension settings.

–enable-sync-oauth

Enable OAuth sign-in for sync.

–enable-sync-tabs

Enable syncing browser sessions.

–enable-sync-tabs-for-other-clients

Enable syncing browser sessions for other synced clients.

–enable-tab-browser-dragging

Enables tab dragging to create a real browser.

–enable-tab-groups-context-menu

Enables context menu for selecting groups of tabs.

–enable-tcp-fastopen

Enable use of experimental TCP sockets API for sending data in the SYN packet.

–enable-threaded-compositing

Enable multithreaded GPU compositing of web content.

–enable-touch-events

Enable support for JavaScript touch events.

–enable-video-track

Enables support for video tracks. Current implementation is incomplete and this flag is used for development and testing.

–enable-visual-word-movement

Enables moving cursor by word in visual order.

–enable-watchdog

Spawn threads to watch for excessive delays in specified message loops. User should set breakpoints on Alarm() to examine problematic thread. Usage: -enable-watchdog=[ui][io] Order of the listed sub-arguments does not matter.

–enable-website-settings

Enable Website Settings. The Website Settings UI will replace the Page Info Bubble.

–enable-websocket-over-spdy

Use WebSocket over SPDY.

–enable-webstore-link

Enables the web store link experiment.

–enabled

enabled: Both prerendering and prefetching.

–enterprise-enrollment-initial-modulus[3]

Power of the power-of-2 initial modulus that will be used by the auto-enrollment client. E.g. "4" means the modulus will be 2^4 = 16.

–enterprise-enrollment-modulus-limit[3]

Power of the power-of-2 maximum modulus that will be used by the auto-enrollment client.

–experimental-location-features

Enables experimental features for the geolocation API. Current features: – CoreLocation support for Mac OS X 10.6 – Gateway location for Linux and Windows – Location platform support for Windows 7

–experimental-spellchecker-features

Enables experimental features for Spellchecker. Right now, the first experimental feature is auto spell correct, which corrects words which are misppelled by typing the word with two consecutive letters swapped. The features that will be added next are: 1 – Allow multiple spellcheckers to work simultaneously. 2 – Allow automatic detection of spell check language. TODO(sidchat): Implement the above fetaures to work under this flag.

–explicitly-allowed-ports

Explicitly allow additional ports using a comma separated list of port numbers.

–extension-process

Marks a renderer as extension process.

–extensions-update-frequency

Frequency in seconds for Extensions auto-update.

–external-autofill-popup

Should we use an external Autofill popup? Default is no.

–extra-plugin-dir

Load NPAPI plugins from the specified directory.

–feedback-server

Alternative feedback server to use when submitting user feedback

–file-descriptor-limit

The file descriptor limit is set to the value of this switch, subject to the OS hard limits. Useful for testing that file descriptor exhaustion is handled gracefully.

–filemgr-ext-path[2]

Enables overriding the path off file manager extension.

–first-run

Display the First Run experience when the browser is started, regardless of whether or not it’s actually the first run.

–flag-switches-begin

These two flags are added around the switches about:flags adds to the command line. This is useful to see which switches were added by about:flags on about:version. They don’t have any effect.

–flag-switches-end

No description

–focus-existing-tab-on-open

If true opening a url from the omnibox attepts to focus an existing tab.

–force-apps-promo-visible

Forces the apps/webstore promo to be shown, independent of whether it has timed out, etc. Useful for testing.

–force-compositing-mode

If accelerated compositing is supported, always enter compositing mode for the base layer even when compositing is not strictly required.

–force-fieldtest

Some field tests may rendomized in the browser, and the randomly selected outcome needs to be propogated to the renderer. For instance, this is used to modify histograms recorded in the renderer, or to get the renderer to also set of its state (initialize, or not initialize components) to match the experiment(s). The argument is a string-ized list of experiment names, and the associated value that was randomly selected. In the recent implementetaion, the persistent representation generated by field_trial.cc and later decoded, is a list of name and value pairs, separated by slashes. See field trial.cc for current details.

–force-renderer-accessibility

Force renderer accessibility to be on instead of enabling it on demand when a screen reader is detected. The disable-renderer-accessibility switch overrides this if present.

–full-memory-crash-report

Generates full memory crash dump.

–gaia-host

Specify the backend server used for gaia authentications, like sync or policies for example. The https:// prefix and the trailing slash should be omitted. The default value is "www.google.com".

–gaia-profile-info

Enables using GAIA information to populate profile name and icon.

–gpu-launcher

Extra command line options for launching the GPU process (normally used for debugging). Use like renderer-cmd-prefix.

–gpu-no-context-lost

Inform Chrome that a GPU context will not be lost in power saving mode, screen saving mode, etc. Note that this flag does not ensure that a GPU context will never be lost in any situations, say, a GPU reset.

–gpu-process

Makes this process a GPU sub-process.

–gpu-startup-dialog

Causes the GPU process to display a dialog on launch.

–gssapi-library-name

Specifies a custom name for the GSSAPI library to load.

–h

No description

–help

These flags show the man page on Linux. They are equivalent to each other.

–hidden

The field trial is forced into the HIDDEN_EXPERIMENT group.

–hide-icons

Make Windows happy by allowing it to show "Enable access to this program" checkbox in Add/Remove Programs->Set Program Access and Defaults. This only shows an error box because the only way to hide Chrome is by uninstalling it.

–homepage

The value of this switch specifies which page will be displayed in newly-opened tabs. We need this for testing purposes so that the UI tests don’t depend on what comes up for http://google.com.

–host-resolver-parallelism

The maximum number of concurrent host resolve requests (i.e. DNS) to allow.

–host-resolver-retry-attempts

The maximum number of retry attempts to resolve the host. Set this to zero to disable host resolver retry attempts.

–host-resolver-rules

These mappings only apply to the host resolver.

–host-rules

Comma separated list of rules that control how hostnames are mapped. For example: "MAP * 127.0.0.1" –> Forces all hostnames to be mapped to 127.0.0.1 "MAP *.google.com proxy" –> Forces all google.com subdomains to be resolved to "proxy". "MAP test.com [::1]:77 –> Forces "test.com" to resolve to IPv6 loopback. Will also force the port of the resulting socket address to be 77. "MAP * baz, EXCLUDE http://www.google.com"; –> Remaps everything to "baz", except for "www.google.com". These mappings apply to the endpoint host in a net::URLRequest (the TCP connect and host resolver in a direct connection, and the CONNECT in an http proxy connection, and the endpoint host in a SOCKS proxy connection).

–hsts-hosts

This switch will take the JSON-formatted HSTS specification and load it as if it were a preloaded HSTS entry. It will take precedence over both website-specified rules and built-in rules. The JSON format is the same as that persisted in <profile_dir>/Default/TransportSecurity

–ignore-certificate-errors

Ignore certificate related errors.

–ignore-gpu-blacklist

Ignores GPU blacklist.

–import

Perform importing from another browser. The value associated with this setting encodes the target browser and what items to import.

–import-from-file

Perform bookmark importing from an HTML file. The value associated with this setting encodes the file path. It may be used jointly with kImport.

–in-process-gpu

Run the GPU process as a thread in the browser process.

–in-process-plugins

Runs plugins inside the renderer process

–in-process-webgl

Runs WebGL inside the renderer process.

–incognito

Causes the browser to launch directly in incognito mode.

–instant

The field trial is forced into the INSTANT_EXPERIMENT group.

–instant-field-trial

Control the Instant field trial. Valid values are defined below. If an unknown value is supplied on the command line, the field trial is disabled.

–instant-url

URL to use for instant. If specified this overrides the url from the TemplateURL.

–invert-web-content

Invert web content pixels, for users who prefer white-on-black. (Temporary, just during development and testing of this feature.)

–js-flags

Specifies the flags passed to JS engine

–keep-alive-for-test

Used for testing – keeps browser alive after last browser window closes.

–kiosk[10]

Enable Kiosk mode.

–kiosk-printing[10]

Print automatically in kiosk mode. |kKioskMode| must be set as well. See http://crbug.com/31395.

–lang[3]

Use the given language for UI in the input method candidate window.

–load-component-extension

Comma-separated list of directories with component extensions to load.

–load-extension

Load an extension from the specified directory.

–load-opencryptoki

Load the opencryptoki library into NSS at startup. This is only needed temporarily for developers who need to work on WiFi/VPN certificate code. TODO(gspencer): Remove this switch once cryptohomed work is finished: http://crosbug.com/12295 and http://crosbug.com/12304

–load-plugin

Load an NPAPI plugin from the specified path.

–locale_pak

Load the locale resources from the given path. When running on Mac/Unix the path should point to a locale.pak file.

–log-level

Sets the minimum log level. Valid values are from 0 to 3: INFO = 0, WARNING = 1, LOG_ERROR = 2, LOG_FATAL = 3.

–log-net-log

Enable displaying net log events on the command line, or writing the events to a separate file if a file name is given.

–log-plugin-messages

Make plugin processes log their sent and received messages to VLOG(1).

–login-manager[3]

Enable Chrome-as-a-login-manager behavior.

–login-password[3]

Specifies a password to be used to login (along with login-user).

–login-profile[3]

Specifies the profile to use once a chromeos user is logged in.

–login-screen[3]

Allows to override the first login screen. The value should be the name of the first login screen to show (see chrome/browser/chromeos/login/login_wizard_view.cc for actual names). Ignored if kLoginManager is not specified. TODO(avayvod): Remove when the switch is no longer needed for testing.

–login-screen-size[3]

Allows control over the initial login screen size. Pass width,height.

–login-user[3]

Specifies the user which is already logged in.

–make-default-browser

Make Chrome default browser

–max-spdy-concurrent-streams

Set the maximum concurrent streams over a SPDY session.

–max-spdy-sessions-per-domain

Set the maximum SPDY sessions per domain.

–media-cache-size

Forces the maximum disk space to be used by the media cache, in bytes.

–memory-profile

Enable dynamic loading of the Memory Profiler DLL, which will trace all memory allocations during the run.

–memory-widget[3]

Shows a memory consumption status area widget for OOM debugging.

–message-loop-histogrammer

Enable histograming of tasks served by MessageLoop. See about:histograms/Loop for results, which show frequency of messages on each thread, including APC count, object signalling count, etc.

–metrics-recording-only

Enables the recording of metrics reports but disables reporting. In contrast to kDisableMetrics, this executes all the code that a normal client would use for reporting, except the report is dropped rather than sent to the server. This is useful for finding issues in the metrics code during UI and performance tests.

–mock

No description

–multi-profiles

Enables multiprofile Chrome.

–nacl-broker

Causes the process to run as a NativeClient broker (used for launching NaCl loader processes on 64-bit Windows).

–nacl-loader

Causes the process to run as a NativeClient loader.

–nacl-loader-cmd-prefix

On POSIX only: the contents of this flag are prepended to the nacl-loader command line. Useful values might be "valgrind" or "xterm -e gdb –args".

–net-log-level

Sets the base logging level for the net log. Log 0 logs the most data. Intended primarily for use with –log-net-log.

–new-window

Launch URL in new browser window.

–no-default-browser-check

Disables the default browser check. Useful for UI/browser tests where we want to avoid having the default browser info-bar displayed.

–no-displaying-insecure-content

By default, an https page can load images, fonts or frames from an http page. This switch overrides this to block this lesser mixed-content problem.

–no-events

Don’t record/playback events when using record & playback.

–no-experiments

Bypass the First Run experience when the browser is started, regardless of Disables all experiments set on about:flags. Does not disable about:flags itself. Useful if an experiment makes chrome crash at startup: One can start chrome with –no-experiments, disable the problematic lab at about:flags and then restart chrome without this switch again.

–no-first-run

whether or not it’s actually the first run. Overrides kFirstRun in case you’re for some reason tempted to pass them both.

–no-js-randomness

Support a separate switch that enables the v8 playback extension. The extension causes javascript calls to Date.now() and Math.random() to return consistent values, such that subsequent loads of the same page will result in consistent js-generated data and XHR requests. Pages may still be able to generate inconsistent data from plugins.

–no-message-box

Disable ui::MessageBox. This is useful when running as part of scripts that do not have a user interface.

–no-pings

Don’t send hyperlink auditing pings

–no-process-singleton-dialog[9]

Bypass the error dialog when the profile lock couldn’t be attained. This switch is used during automated testing.

–no-protector

Disables the Protector feature.

–no-proxy-server

Don’t use a proxy server, always make direct connections. Overrides any other proxy server flags that are passed.

–no-referrers

Don’t send HTTP-Referer headers.

–no-running-insecure-content

Stronger version of insecure content blocking, for the case where the blocking would only be applied to a whitelist of domains. Switch is expected to become obsolete once the whitelist goes away.

–no-sandbox

Disables the sandbox for all process types that are normally sandboxed.

–no-service-autorun

Disables the service process from adding itself as an autorun process. This does not delete existing autorun registrations, it just prevents the service from registering a new one.

–no-startup-window

Does not automatically open a browser window on startup (used when launching Chrome for the purpose of hosting background apps).

–noerrdialogs

Suppresses all error dialogs when present.

–notify-cp-token-expired

Show a desktop notification that the cloud print token has expired and that user needs to re-authenticate.

–ntp-app-install-hint

Shows a [+] at the end of apps pages on the NTP.

–num-pac-threads

Specifies the maximum number of threads to use for running the Proxy Autoconfig (PAC) script.

–omnibox-aggressive-with-history-url

Controls whether the omnibox’s HistoryURL provider is aggressive.

–omnibox-inline-history-quick-provider-allowed

Controls whether the omnibox’s HistoryQuickProvider is allowed to inline suggestions.

–only-block-setting-third-party-cookies

When the option to block third-party cookies is enabled, only block third-party cookies from being set.

–oobe-skip-postlogin[2]

Skips all other OOBE pages after user login.

–organic

Simulate an organic Chrome install.

–osmesa

No description

–pack-extension

Package an extension to a .crx installable file from a given directory.

–pack-extension-key

Optional PEM private key is to use in signing packaged .crx.

–parent-profile

Specifies the path to the user data folder for the parent profile.

–password-store[11]

Specifies which password store to use (detect, default, gnome, kwallet).

–playback-mode

Read previously recorded data from the cache. Only cached data is read. See kRecordMode.

–plugin

Causes the process to run as a plugin subprocess.

–plugin-launcher

Specifies a command that should be used to launch the plugin process. Useful for running the plugin process through purify or quantify. Ex: –plugin-launcher="path\to\purify /Run=yes"

–plugin-path

Tells the plugin process the path of the plugin to load

–plugin-startup-dialog

Causes the plugin process to display a dialog on launch.

–ppapi

Argument to the process type that indicates a PPAPI plugin process type.

–ppapi-broker

Argument to the process type that indicates a PPAPI broker process type.

–ppapi-flash-args

"Command-line" arguments for the PPAPI Flash; used for debugging options.

–ppapi-flash-in-process

Forces the PPAPI version of Flash (if it’s being used) to run in the renderer process rather than in a separate plugin process.

–ppapi-flash-path

Use the PPAPI (Pepper) Flash found at the given path.

–ppapi-flash-version

Report the given version for the PPAPI (Pepper) Flash. The version should be numbers separated by ‘.’s (e.g., "12.3.456.78"). If not specified, it defaults to "10.2.999.999".

–ppapi-out-of-process

Runs PPAPI (Pepper) plugins out-of-process.

–ppapi-plugin-launcher

Like kPluginLauncher for PPAPI plugins.

–ppapi-startup-dialog

Causes the PPAPI sub process to display a dialog on launch.

–prefetch_only

prefetch_only: No prerendering, but enable prefetching.

–preload-instant-search

Aggressively preload the default search engine’s Instant URL, so it’s ready to receive queries. Only has an effect if Instant is turned on (via "Enable Instant for faster searching and browsing" in Preferences -> Basics).

–prerender

Controls speculative prerendering of pages, and content prefetching. Both are dispatched from <link rel=prefetch href=…> elements.

–prerender-from-omnibox

Trigger prerendering of pages from suggestions in the omnibox. Only has an effect when Instant is either disabled or restricted to search, and when prerender is enabled.

–print

Prints the pages on the screen.

–process-per-site

Runs a single process for each site (i.e., group of pages from the same registered domain) the user visits. We default to using a renderer process for each site instance (i.e., group of pages from the same registered domain with script connections to each other).

–process-per-tab

Runs each set of script-connected tabs (i.e., a BrowsingInstance) in its own renderer process. We default to using a renderer process for each site instance (i.e., group of pages from the same registered domain with script connections to each other).

–product-version

Output the product version information and quit. Used as an internal api to detect the installed version of Chrome on Linux.

–profile-directory

Selects directory of profile to associate with the first browser launched.

–profiling-at-start

Starts the sampling based profiler for the browser process at startup. This will only work if chrome has been built with the gyp variable profiling=1. The output will go to the value of kProfilingFile.

–profiling-file

Specifies a location for profiling output. This will only work if chrome has been built with the gyp variable profiling=1. {pid} if present will be replaced by the pid of the process. {count} if present will be incremented each time a profile is generated for this process. The default is chrome-profile-{pid}.

–profiling-flush

Controls whether profile data is periodically flushed to a file. Normally the data gets written on exit but cases exist where chrome doesn’t exit cleanly (especially when using single-process). A time in seconds can be specified.

–profiling-output-file

Specifies a path for the output of task-level profiling which can be loaded and viewed in about:profiler.

–promo-server-url

Specifies a custom URL for fetching NTP promo data.

–proxy-auto-detect

Force proxy auto-detection.

–proxy-bypass-list

Specify a list of hosts for whom we bypass proxy settings and use direct connections. Ignored if –proxy-auto-detect or –no-proxy-server are also specified. This is a comma separated list of bypass rules. See: "net/proxy/proxy_bypass_rules.h" for the format of these rules.

–proxy-pac-url

Use the pac script at the given URL

–proxy-server

Use a specified proxy server, overrides system settings. This switch only affects HTTP and HTTPS requests.

–purge-memory-button

Adds a "Purge memory" button to the Task Manager, which tries to dump as much memory as possible. This is mostly useful for testing how well the MemoryPurger functionality works. NOTE: This is only implemented for Views.

–record-mode

Chrome supports a playback and record mode. Record mode saves *everything* to the cache. Playback mode reads data exclusively from the cache. This allows us to record a session into the cache and then replay it at will. See also kPlaybackMode.

–reduce-gpu-sandbox

Reduces the GPU process sandbox to be less strict.

–register-pepper-plugins

Register Pepper plugins (see pepper_plugin_registry.cc for its format).

–relauncher[5]

A process type (switches::kProcessType) that relaunches the browser. See chrome/browser/mac/relauncher.h.

–reload-killed-tabs

Reload pages that have been killed when they are next focused by the user.

–remote-debugging-frontend

Uses custom front-end URL for the remote debugging.

–remote-debugging-port

Enable remote debug over HTTP on the specified port.

–renderer

Causes the process to run as renderer instead of as browser.

–renderer-assert-test

Causes the renderer process to throw an assertion on launch.

–renderer-check-false-test[12]

Causes the renderer process to throw an assertion on launch.

–renderer-cmd-prefix

On POSIX only: the contents of this flag are prepended to the renderer command line. Useful values might be "valgrind" or "xterm -e gdb –args".

–renderer-crash-test

Causes the renderer process to crash on launch.

–renderer-print-preview

Enables print preview in the renderer. This flag is generated internally by Chrome and does nothing when directly passed to the browser.

–renderer-process-limit

Overrides the default/calculated limit to the number of renderer processes. Very high values for this setting can lead to high memory/resource usage or instability.

–renderer-startup-dialog

Causes the renderer process to display a dialog on launch.

–restore-last-session

Indicates the last session should be restored on startup. This overrides the preferences value and is primarily intended for testing. The value of this switch is the number of tabs to wait until loaded before ‘load completed’ is sent to the ui_test.

–safebrowsing-disable-auto-update

If present, safebrowsing only performs update when SafeBrowsingProtocolManager::ForceScheduleNextUpdate() is explicitly called. This is used for testing only.

–safebrowsing-disable-download-protection

TODO(lzheng): Remove this flag once the feature works fine (http://crbug.com/74848). This flag disables safebrowsing feature that checks download url and download content’s hash to make sure the content are not malicious.

–safebrowsing-info-url-prefix

URL prefix used by safebrowsing to fetch hash, download data and report malware.

–safebrowsing-mackey-url-prefix

URL prefix used by safebrowsing to get MAC key.

–scroll-pixels[1]

Specify the amount the trackpad should scroll by.

–search-in-omnibox-hint

Enables the showing of an info-bar instructing user they can search directly from the omnibox.

–service

Causes the process to run as a service process.

–service-account-lsid

The LSID of the account to use for the service process.

–set-token[2]

Sets a token in the token service, for testing.

–show-autofill-type-predictions

Annotate forms with Autofill field type predictions.

–show-component-extension-options

Makes component extensions appear in chrome://settings/extensions.

–show-composited-layer-borders

Renders a border around composited Render Layers to help debug and study layer compositing.

–show-composited-layer-tree

Draws a textual dump of the compositor layer tree to help debug and study layer compositing.

–show-fps-counter

Draws a FPS indicator

–show-icons

See kHideIcons.

–show-paint-rects

Visibly render a border around paint rects in the web page to help debug and study painting behavior.

–show-volume-status[3]

Show volume controls in status bar on ChromeOS.

–silent

The field trial is forced into the SILENT_EXPERIMENT group.

–silent-dump-on-dcheck

Change the DCHECKS to dump memory and continue instead of displaying error dialog. This is valid only in Release mode when –enable-dcheck is specified.

–simulate-upgrade

Simulates an update being available.

–single-process

Runs the renderer and plugins in the same process as the browser

–skip-gpu-data-loading

Skip gpu info collection, blacklist loading, and blacklist auto-update scheduling at browser startup time. Therefore, all GPU features are available, and about:gpu page shows empty content. The switch is intended only for tests.

–skip-oauth-login[3]

Skips OAuth part of ChromeOS login process.

–socket-reuse-policy

Choose the socket reuse policy specified. The value should be of type enum ClientSocketReusePolicy.

–start-maximized

Start the browser maximized, regardless of any previous settings.

–stub-cros[3]

Indicates that stub implementations of the libcros library should be used. This is typically used to test the chromeos build of chrome on the desktop.

–stub-cros-settings[3]

Indicates that a stub implementation of CrosSettings that stores settings in memory without signing should be used, treating current user as the owner. This option is for testing the chromeos build of chrome on the desktop only.

–suggest

The field trial is forced into the SUGGEST_EXPERIMENT group.

–swiftshader

No description

–swiftshader-path

No description

–sync-allow-insecure-xmpp-connection

Allow insecure XMPP connections for sync (for testing).

–sync-invalidate-xmpp-login

Invalidate any login info passed into sync’s XMPP connection.

–sync-notification-host

Override the default host used for sync notifications. Can be either "host" or "host:port".

–sync-notification-method

Override the default notification method for sync.

–sync-promo-version

Specifies the sync promo version to display.

–sync-throw-unrecoverable-error

Makes the sync code to throw an unrecoverable error after initialization. Useful for testing unrecoverable error scenarios.

–sync-try-ssltcp-first-for-xmpp

Try to connect to XMPP using SSLTCP first (for testing).

–sync-url

Override the default server used for profile sync.

–test-child-process

When running certain tests that spawn child processes, this switch indicates to the test framework that the current process is a child process.

–test-gl-lib

Flag used for Linux tests: for desktop GL bindings, try to load this GL library first, but fall back to regular library if loading fails.

–test-load-libcros[3]

Attempts to load libcros and validate it, then exits. A nonzero return code means the library could not be loaded correctly.

–test-nacl-sandbox

Runs the security test for the NaCl loader sandbox.

–test-name

Pass the name of the current running automated test to Chrome.

–test-sandbox

Runs the security test for the renderer sandbox.

–test-type

Pass the type of the current test harness ("browser" or "ui")

–testing-channel

The value of this switch tells the app to listen for and broadcast testing-related messages on IPC channel with the given ID.

–testing-fixed-http-port

Allows for forcing socket connections to http/https to use fixed ports.

–testing-fixed-https-port

No description

–touch-devices[13]

Tells chrome to interpret events from these devices as touch events. Only available with XInput 2 (i.e. X server 1.8 or above). The id’s of the devices can be retrieved from ‘xinput list’.

–touch-optimized-ui

Enables UI changes that make it easier to use with a touchscreen.

–trace-startup

Causes TRACE_EVENT flags to be recorded from startup. Optionally, can specify the specific trace categories to include (e.g. –trace-startup=base,net) otherwise, all events are recorded. Setting this flag results in the first call to BeginTracing() to receive all trace events since startup. In Chrome, you may find –trace-startup-file and –trace-startup-duration to control the auto-saving of the trace (not supported in the base-only TraceLog component).

–trace-startup-duration

Sets the time in seconds until startup tracing ends. If omitted a default of 5 seconds is used. Has no effect without –trace-startup, or if –startup-trace-file=none was supplied.

–trace-startup-file

If supplied, sets the file which startup tracing will be stored into, if omitted the default will be used "chrometrace.log" in the current directory. Has no effect unless –trace-startup is also supplied. Example: –trace-startup –trace-startup-file=/tmp/trace_event.log As a special case, can be set to ‘none’ – this disables automatically saving the result to a file and the first manually recorded trace will then receive all events since startup.

–try-chrome-again

Experimental. Shows a dialog asking the user to try chrome. This flag is to be used only by the upgrade process.

–type

The value of this switch determines whether the process is started as a renderer or plugin host. If it’s empty, it’s the browser.

–uninstall

Runs un-installation steps that were done by chrome first-run.

–uninstall-extension

Uninstall an extension with the specified extension id.

–use-gl

Select which implementation of GL the GPU process should use. Options are: desktop: whatever desktop OpenGL the user has installed (Linux and Mac default). egl: whatever EGL / GLES2 the user has installed (Windows default – actually ANGLE). osmesa: The OSMesa software renderer.

–use-mock-keychain[5]

Use mock keychain for testing purposes, which prevents blocking dialogs from causing timeouts.

–use-pulseaudio

Use PulseAudio instead of ALSA on Linux.

–use-spdy

Use Spdy for the transport protocol instead of HTTP. This is a temporary testing flag.

–use-system-ssl[14]

Use the system SSL library (Secure Transport on Mac, SChannel on Windows) instead of NSS for SSL.

–user-agent

A string used to override the default user agent with a custom one.

–user-data-dir

Specifies the user data directory, which is where the browser will look for all of its state.

–utility

Causes the process to run as a utility subprocess.

–utility-allowed-dir

The utility process is sandboxed, with access to one directory. This flag specifies the directory that can be accessed.

–utility-cmd-prefix

On POSIX only: the contents of this flag are prepended to the utility process command line. Useful values might be "valgrind" or "xterm -e gdb –args".

–v

Gives the default maximal active V-logging level; 0 is the default. Normally positive values are used for V-logging levels.

–version

Print version information and quit.

–video-threads

Set number of threads to use for video decoding.

–vmodule

Gives the per-module maximal V-logging levels to override the value given by –v. E.g. "my_module=2,foo*=3" would change the logging level for all code in source files "my_module.*" and "foo*.*" ("-inl" suffixes are also disregarded for this matching). Any pattern containing a forward or backward slash will be tested against the whole pathname and not just the module. E.g., "*/foo/bar/*=2" would change the logging level for all code in source files under a "foo/bar" directory.

–wait-for-debugger

Will wait for 60 seconds for a debugger to come to attach to the process.

–wait-for-debugger-children

Will add kWaitForDebugger to every child processes. If a value is passed, it will be used as a filter to determine if the child process should have the kWaitForDebugger flag passed on or not.

–web-worker-process-per-core

Causes the worker process allocation to use as many processes as cores.

–web-worker-share-processes

Causes workers to run together in one process, depending on their domains. Note this is duplicated in webworkerclient_impl.cc

–webcore-log-channels

Choose which logging channels in WebCore to activate. See Logging.cpp in WebKit’s WebCore for a list of available channels.

–webui-login[3]

Enable WebUI based login screens.

–webui-task-manager

Use experimental WebUI task manager dialog.

–whitelisted-extension-id

Adds the given extension ID to all the permission whitelists.

–window-position

Specify the initial window position: –window-position=x,y

–window-size

Specify the initial window size: –window-size=w,h

–winhttp-proxy-resolver

Use WinHTTP to fetch and evaluate PAC scripts. Otherwise the default is to use Chromium’s network stack to fetch, and V8 to evaluate.

–worker

Causes the process to run as a worker subprocess.

–zygote

Causes the process to run as a renderer zygote.

How to use a command line switch?

The Chromium Team has made a page on which they briefly explain how to use these switches.

Conditions

These are rather technical. While most are pretty self-explanatory, keep in mind that any condition means that a switch isn’t always available.

1. The constant OS_LINUX must be defined.

2. The constant NDEBUG must not be defined.

3. The constant OS_CHROMEOS must be defined.

4. The constant TOOLKIT_VIEWS must be defined.

5. The constant OS_MACOSX must be defined.

6. The constant OS_WIN must be defined.

7. The constant OS_CHROMEOS must not be defined, and the constant GOOGLE_CHROME_BUILD must be defined.

8. The constant OS_POSIX must not be defined, and the constants OS_CHROMEOS and OS_MACOSX must be defined.

9. The constant OS_POSIX must be defined.

10. The constant OS_MACOSX must not be defined.

11. The constants OS_CHROMEOS and OS_MACOSX must not be defined.

12. The constant OFFICIAL_BUILD must not be defined.

13. The constant HAVE_XINPUT2 must be defined.

14. The constants OS_MACOSX and OS_WIN must be defined.

Sources: chrome_switches.cc, generated JSON data and my generator source-code. The list will automagically be updated around midnight GMT.

 

Source: List of Chromium Command Line Switches « Peter Beverloo

Categories: Browsers

How to: Simulate Mouse and Keyboard Events in Code

February 22, 2012 Leave a comment

Windows Forms provides several options for programmatically simulating mouse and keyboard input. This topic provides an overview of these options.

Simulating Mouse Input


The best way to simulate mouse events is to call the OnEventName method that raises the mouse event you want to simulate. This option is usually possible only within custom controls and forms, because the methods that raise events are protected and cannot be accessed outside the control or form. For example, the following steps illustrate how to simulate clicking the right mouse button in code.

To programmatically click the right mouse button
  1. Create a MouseEventArgs whose Button property is set to the MouseButtons.Right value.

  2. Call the OnMouseClick method with this MouseEventArgs as the argument.

For more information on custom controls, see Developing Windows Forms Controls at Design Time.

There are other ways to simulate mouse input. For example, you can programmatically set a control property that represents a state that is typically set through mouse input (such as the Checked property of the CheckBox control), or you can directly call the delegate that is attached to the event you want to simulate.

Simulating Keyboard Input


Although you can simulate keyboard input by using the strategies discussed above for mouse input, Windows Forms also provides the SendKeys class for sending keystrokes to the active application.

Caution noteCaution

If your application is intended for international use with a variety of keyboards, the use of SendKeys.Send could yield unpredictable results and should be avoided.

NoteNote

The SendKeys class has been updated for the .NET Framework 3.0 to enable its use in applications that run on Windows Vista. The enhanced security of Windows Vista (known as User Account Control or UAC) prevents the previous implementation from working as expected.

The SendKeys class is susceptible to timing issues, which some developers have had to work around. The updated implementation is still susceptible to timing issues, but is slightly faster and may require changes to the workarounds. The SendKeys class tries to use the previous implementation first, and if that fails, uses the new implementation. As a result, the SendKeys class may behave differently on different operating systems. Additionally, when the SendKeys class uses the new implementation, the SendWait method will not wait for messages to be processed when they are sent to another process.

If your application relies on consistent behavior regardless of the operating system, you can force the SendKeys class to use the new implementation by adding the following application setting to your app.config file.

<appSettings>

<add key="SendKeys" value="SendInput"/>

</appSettings>

To force the SendKeys class to use the previous implementation, use the value "JournalHook" instead.

To send a keystroke to the same application
  • Call the Send or SendWait method of the SendKeys class. The specified keystrokes will be received by the active control of the application. The following code example uses Send to simulate pressing the ENTER key when the user double-clicks the surface of the form. This example assumes a Form with a single Button control that has a tab index of 0.

    C#

    C++

    VB

    Copy

    ' Send a key to the button when the user double-clicks anywhere 
    ' on the form.
    Private Sub Form1_DoubleClick(ByVal sender As Object, _
        ByVal e As EventArgs) Handles Me.DoubleClick
    
        ' Send the enter key to the button, which raises the click 
        ' event for the button. This works because the tab stop of 
        ' the button is 0.
        SendKeys.Send("{ENTER}")
    End Sub
To send a keystroke to a different application
  • Activate the application window that will receive the keystrokes, and then call the Send or SendWait method. Because there is no managed method to activate another application, you must use native Windows methods to force focus on other applications. The following code example uses platform invoke to call the FindWindow and SetForegroundWindow methods to activate the Calculator application window, and then calls SendWait to issue a series of calculations to the Calculator application.

    NoteNote

    The correct parameters of the FindWindow call that locates the Calculator application vary based on your version of Windows. The following code finds the Calculator application on Windows 7. On Windows Vista, change the first parameter to "SciCalc". You can use the Spy++ tool, included with Visual Studio, to determine the correct parameters.

    C#

    C++

    VB

    Copy

    ' Get a handle to an application window.
    Declare Auto Function FindWindow Lib "USER32.DLL" ( _
        ByVal lpClassName As String, _
        ByVal lpWindowName As String) As IntPtr
    
    ' Activate an application window.
    Declare Auto Function SetForegroundWindow Lib "USER32.DLL" _
        (ByVal hWnd As IntPtr) As Boolean
    
    ' Send a series of key presses to the Calculator application.
    Private Sub button1_Click(ByVal sender As Object, _
        ByVal e As EventArgs) Handles button1.Click
    
        ' Get a handle to the Calculator application. The window class
        ' and window name were obtained using the Spy++ tool.
        Dim calculatorHandle As IntPtr = FindWindow("CalcFrame", "Calculator")
    
        ' Verify that Calculator is a running process.
        If calculatorHandle = IntPtr.Zero Then
            MsgBox("Calculator is not running.")
            Return
        End If
    
        ' Make Calculator the foreground application and send it 
        ' a set of calculations.
        SetForegroundWindow(calculatorHandle)
        SendKeys.SendWait("111")
        SendKeys.SendWait("*")
        SendKeys.SendWait("11")
        SendKeys.SendWait("=")
    End Sub

Example


The following code example is the complete application for the previous code examples.

C#

C++

VB

Copy

Imports System
Imports System.Runtime.InteropServices
Imports System.Drawing
Imports System.Windows.Forms

Namespace SimulateKeyPress

    Class Form1
        Inherits Form
        Private WithEvents button1 As New Button()

        <STAThread()> _
        Public Shared Sub Main()
            Application.EnableVisualStyles()
            Application.Run(New Form1())
        End Sub

        Public Sub New()
            button1.Location = New Point(10, 10)
            button1.TabIndex = 0
            button1.Text = "Click to automate Calculator"
            button1.AutoSize = True
            Me.Controls.Add(button1)
        End Sub

        ' Get a handle to an application window.
        Declare Auto Function FindWindow Lib "USER32.DLL" ( _
            ByVal lpClassName As String, _
            ByVal lpWindowName As String) As IntPtr

        ' Activate an application window.
        Declare Auto Function SetForegroundWindow Lib "USER32.DLL" _
            (ByVal hWnd As IntPtr) As Boolean

        ' Send a series of key presses to the Calculator application.
        Private Sub button1_Click(ByVal sender As Object, _
            ByVal e As EventArgs) Handles button1.Click

            ' Get a handle to the Calculator application. The window class
            ' and window name were obtained using the Spy++ tool.
            Dim calculatorHandle As IntPtr = FindWindow("CalcFrame", "Calculator")

            ' Verify that Calculator is a running process.
            If calculatorHandle = IntPtr.Zero Then
                MsgBox("Calculator is not running.")
                Return
            End If

            ' Make Calculator the foreground application and send it 
            ' a set of calculations.
            SetForegroundWindow(calculatorHandle)
            SendKeys.SendWait("111")
            SendKeys.SendWait("*")
            SendKeys.SendWait("11")
            SendKeys.SendWait("=")
        End Sub

        ' Send a key to the button when the user double-clicks anywhere 
        ' on the form.
        Private Sub Form1_DoubleClick(ByVal sender As Object, _
            ByVal e As EventArgs) Handles Me.DoubleClick

            ' Send the enter key to the button, which raises the click 
            ' event for the button. This works because the tab stop of 
            ' the button is 0.
            SendKeys.Send("{ENTER}")
        End Sub

    End Class
End Namespace

Compiling the Code


This example requires:

  • References to the System, System.Drawing and System.Windows.Forms assemblies.

For information about building this example from the command line for Visual Basic or Visual C#, see Building from the Command Line (Visual Basic) or Command-line Building With csc.exe. You can also build this example in Visual Studio by pasting the code into a new project. For more information, see How to: Compile and Run a Complete Windows Forms Code Example Using Visual Studio and How to: Compile and Run a Complete Windows Forms Code Example Using Visual Studio and How to: Compile and Run a Complete Windows Forms Code Example Using Visual Studio and How to: Compile and Run a Complete Windows Forms Code Example Using Visual Studio and How to: Compile and Run a Complete Windows Forms Code Example Using Visual Studio.

 

Source: How to: Simulate Mouse and Keyboard Events in Code

Categories: Programming

Known Issues with Chrome Automation using Send Keys

February 22, 2012 Leave a comment
Categories: Programming, Repackaging

Known Issues with Chrome in XenApp

February 22, 2012 Leave a comment
Categories: Browsers, Citrix
Follow

Get every new post delivered to your Inbox.

Join 212 other followers