chrome

Chrome may refer to: read more at WikiPedia

  • chrome As seen at http://code.google.com/events/io/sessions.html

    Extensions for Google Chrome are Coming :-)

    Developing extensions for Google Chrome
    Chrome

    "Learn how Google Chrome makes it easy to write extensions using the web technologies you already know. This talk will cover the basics of the extension system (distribution/packaging, installation, updates), as well as the different APIs to enhance with the browser."

    Google I/O offers 80+ sessions that present highly technical content on Android, Chrome, App Engine, Google Web Toolkit, AJAX and many more. A subset of the content is currently available, providing you with a preview of what I/O has to offer. We'll be updating this session list so check back frequently.

  • Google Chrome Command Line Switches

    While a lot of them are not interesting for the casual user, some are really interesting for us developers. I put at the top the most interesting one in bold, aka the one I use always.

    From the source file chrome_switches.cc at http://src.chromium.org/svn/trunk/src/chrome/common/chrome_switches.cc The list of switches is evolving so consider looking at source code to check for changes. Right click on Google Chrome desktop icon and use properties

    &160;

    &160;

    &160;

    --enable-sync

    Enable syncing bookmarks to a Google Account.

    --incognito

    Causes the browser to launch directly in incognito mode.

    --disable-hang-monitor Suppresses hang monitor dialogs in renderer processes.
    --disable-metrics Completely disables UMA metrics system.
    --disable-metrics-reporting Disables only the sending of metrics reports. 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.
    --assert-test Causes the browser process to throw an assertion on startup.
    --renderer-assert-test Causes the renderer process to throw an assertion on launch.
    --crash-test Causes the browser process to crash on startup.
    --renderer-crash-test Causes the renderer process to crash on launch.
    --renderer-startup-dialog Causes the renderer process to display a dialog on launch.
    --plugin-startup-dialog Causes the plugin process to display a dialog on launch.
    --testshell-startup-dialog Causes the test shell process to display a dialog on launch.
    --plugin-launcher="path\to\purify /Run=yes"
    --plugin-launcher
    Specifies a command that should be used to launch the plugin process. Useful
    for running the plugin process through purify or quantify.
    --channel The value of this switch tells the child process which
    IPC channel the browser expects to use to communicate with it.
    --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.
    --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.
    --start-renderers-manually When this switch is present, the browser will throw up a dialog box
    asking the user to start a renderer process independently rather
    than launching the renderer itself. (This is useful for debugging.)
    --renderer Causes the process to run as renderer instead of as browser.
    --renderer-path Path to the exe to run for the renderer subprocess
    --plugin Causes the process to run as plugin host
    --single-process Runs the renderer and plugins in the same process as the browser
    --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).
    --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).
    --in-process-plugins Runs plugins inside the renderer process
    --no-sandbox Runs the renderer outside the sandbox.
    --safe-plugins Runs the plugin processes inside the sandbox.
    --trusted-plugins Excludes these plugins from the plugin sandbox.
    This is a comma separated list of plugin dlls name and activex clsid.
    --test-sandbox Runs the security test for the sandbox.
    --user-data-dir Specifies the user data directory, which is where the browser will look
    for all of its state.
    --app Specifies that the associated value should be launched in "application" mode.
    --upload-file Specifies the file that should be uploaded to the provided application. This
    switch is expected to be used with --app option.
    --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.
    --plugin-path Tells the plugin process the path of the plugin to load
    --js-flags Specifies the flags passed to JS engine
    --geoid The GeoID we should use. This is normally obtained from the operating system
    during first run and cached in the preferences afterwards. This is a numeric
    value; see http://msdn.microsoft.com/en-us/library/ms776390.aspx .
    --lang The language file that we want to try to open. Of the form
    language[-country] where language is the 2 letter code from ISO-639.
    --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.
    --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.
    --log-filter-prefix Will filter log messages to show only the messages that are prefixed
    with the specified value
    --enable-logging Force logging to be enabled. Logging is disabled by default in release
    builds.
    --disable-logging Force logging to be disabled. Logging is enabled by default in debug
    builds.
    --log-level Sets the minimum log level. Valid values are from 0 to 3:
    INFO = 0, WARNING = 1, LOG_ERROR = 2, LOG_FATAL = 3.
    --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.
    --remote-shell-port enable remote debug / automation shell on the specified port
    --uninstall Runs un-installation steps that were done by chrome first-run.
    --omnibox-popup-count Number of entries to show in the omnibox popup.
    &160; &160;
    --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.
    --restore-last-session Indicates the last session should be restored on startup. This overrides
    the preferences value and is primarily intended for testing.
    --record-mode
    --playback-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.
    --no-events Don't record/playback events when using record & playback.
    --hide-icons
    --show-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.
    --make-default-browser Make Chrome default browser
    --proxy-server Use a specified proxy server, overrides system settings. This switch only
    affects HTTP and HTTPS requests.
    --dns-log-details
    --dns-prefetch-disable
    Chrome will support prefetching of DNS information. Until this becomes
    the default, we'll provide a command line switch.
    --debug-print Enables support to debug printing subsystem.
    --allow-all-activex Allow initialization of all activex controls. This is only to help website
    developers test their controls to see if they are compatible in Chrome.
    Note there's a duplicate value in activex_shared.cc (to avoid
    dependency on chrome module). Please change both locations at the same time.
    --disable-dev-tools Browser flag to disable the web inspector for all renderers.
    --always-enable-dev-tools Enable web inspector for all windows, even if they're part of the browser.
    Allows us to use our dev tools to debug browser windows itself.
    --tab-count-to-load-on-session-restore Used to set the value of SessionRestore::num_tabs_to_load_. See
    session_restore.h for details.
    const wchar_t kTabCountToLoadOnSessionRestore[] =
    --memory-profile Enable dynamic loading of the Memory Profiler DLL, which will trace
    all memory allocations during the run.
    --memory-model Configure Chrome's memory model.
    Does chrome really need multiple memory models? No. But we get a lot
    of concerns from individuals about how the changes work on *their*
    system, and we need to be able to experiment with a few choices.
    --enable-file-cookies By default, cookies are not allowed on file://. They are needed in for
    testing, for example page cycler and layout tests. See bug 1157243.
    --start-maximized Start the browser maximized, regardless of any previous settings.
    TODO(pjohnson): Remove this once bug 1137420 is fixed. We are using this
    as a workaround for not being able to use moveTo and resizeTo on a
    top-level window.
    --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.
    --first-run Display the First Run experience when the browser is started, regardless of
    whether or not it's actually the first run.
    --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.
    --import Perform importing from another browser. The value associated with this
    setting encodes the target browser and what items to import.
    --silent-dump-on-dcheck Change the DCHECKS to dump memory and continue instead of crashing.
    This is valid only in Release mode when --enable-dcheck is specified.
    --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-popup-blocking Disable pop-up blocking.
    --disable-javascript Don't execute JavaScript (browser JS like the new tab page still runs).
    --disable-java Prevent Java from running.
    --disable-plugins Prevent plugins from running.
    --disable-images Prevent images from loading.
    --use-lf-heap Use the low fragmentation heap for the CRT.
    --gears-plugin-path Debug only switch to specify which gears plugin dll to load.
    --gears-in-renderer Switch to load Gears in the renderer process.
    --new-http Enable new HTTP stack.
    --javascript-debugger-path Allow loading of the javascript debugger UI from the filesystem.

    --enable-p13n

    &160;
  • google-chrome

    google.chrome
    Google Chrome
    is a web browser developed by Google that uses the WebKit layout engine and application framework. This lightning fast browser has some interesting hidden page only available by typing some special URL in the navigation bar.                                     

    1. about:version
    2. about:memory
    3. about:cache
    4. about:network
    5. about:dns
    6. about:stats
    7. about:histograms
    8. about:plugins
    9. about:internets
    10. about:dns
    11. about:crash

    about:version

    Show information about version of Google Chrome and its internal components.

     google.chrome.about.version

    about:memory

    google.chrome.about.memory

    about:cache

    google.chrome.about.cache 

    about:dns

    about.dns.google.chrome.hidden.page 

    about:histograms

    google.chrome.about.histograms

    about:plugins

    google.chrome.about.plugins

    about:crash

    This is how Google Chrome look like when it crash

    google.chrome.about.crash

    about:internets

    In previous versions of Google Chrome, this should have start the screensavers pipe on windows platform only.

    Following pages are no more working in Google Chrome 3.x and 4.x

    about:network

    about:stats

  • googlechrome Google Chrome Portable is a web browser that runs web pages and applications with lightning speed. It's designed to be simple and stylish. It's packaged as a portable app, so you can take your browsing experience with you. You just need a memory stick with 40MB of space

    Download 3.0.195.27 Rv2

    for Windows, Multilingual - 11MB download / 34MB installed

    Or for the more adventurous the latest build

    Download Google Chrome 4.0 Beta
    for Windows, Multilingual - 11MB download / 34MB installed

    From http://portableapps.com/apps/internet/google_chrome_portable

  • Google Chrome is go for beta on Linux! Thanks to the many Chromium and WebKit developers who helped make Google Chrome a lean, mean browsing machine. Here are a few fun facts from us on the Google Chrome for Linux team:

    • 60,000 lines of Linux-specific code written,
    • 23 developer builds,
    • 2,713 Linux-specific bugs fixed,
    • 12 external committers and bug editors to the Google Chrome for Linux code base,
    • 48 external code contributors.

    Note in the URL the usage of w00t that is used to express joy, particularly that felt during success or victory.

    http://www.google.com/chrome/intl/en/w00t.html

    A lot of people were already using Google Chrome DEV build on Linux (including me with a great stability even in 64 bits), the BETA state means even greater stabilities.

    Related Chrome Articles http://www.waltercedric.com/component/tag/chrome.html

  • chrome-logo

    From Google Blog

    It's been an exciting nine months since welaunched the Google Chrome browser. Already, over 30 million people use it regularly. We designedGoogleChrome for people who live on the web — searching for information, checking email, catching up on the news, shopping or just staying in touch with friends. However, the operating systems that browsers run on were designed in an era where there was no web. So today, we're announcing a new project that's a natural extension of Google Chrome — the Google Chrome Operating System. It's our attempt to re-think what operating systems should be.
    Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.

    read more at http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html

    Linux may get mainstream with Android and Google OS maybe :-)

  • shaunthesheep_google_chrome_3d_css

    The latest version of a Chrome browser show its muscle in version 12 (just restart your chrome browser to get this new version), major new features

    • Hardware accelerated 3D CSS
    • New measures to prevent malware and phishing attempts

    Watch Shaun and his friends' antics in clips from "An Ill Wind", "Snowed In", "The Big Chase", and "Twos Company" through an interactive experiment created with hardware-accelerated HTML5 video, 3D CSS Transforms, and WebM. Use the controls to expand and shrink the video, rotate the scene, bring up a rotating carousel of videos, turn on puddle reflection, and navigate between videos in a snap.

    HTML5 and CSS make these advanced functionalities (and more!) a part of the modern web standard, and allow developers and artists to create immersive, imaginative experiences for everyone to enjoy.

    http://www.chromeexperiments.com/shaunthesheep

    Google is really pushing the web and they show it nicely.

    I am also a fan of Wallace & Gromit as well Smile

  • google_logo

    Nothing is more disturbing than to be redirected to you local Google domain (.ch, .fr, .de or any other) when you want to do a search using English keywords. Did you notice by the way that the index returned is different? you do not get the same number of results or any accurate results at all if you use the same query on your local Google domains…

    Here is a small tip to force Google Chrome to redirect all your direct search (when you type in the location bar and click enter) always to Google.com or any other local domains of Google instead of the one that is revealed by your IP country.

    Under Google Options or you can click on this link chrome://settings/browser

    google_chrome_setSearch_always_to_google_com

    Click on Button manage Search Engine

    Add a new engine, I did name it “always google.com” in my example and use this URL

    http://www.google.com/search?{google:rlz}{google:acceptedsuggestion}{google:originalqueryforsuggestion}sourceid=chrome&ie={inputencoding}&q=%s

    google_chrome_setSearch_always_to_google_com_2

    You can then click on this new search and make it as default

    Additionally you can also set your homepage to www.google.com/ncr to always have the global domains and avoid being redirected to Google.ch

  • logo-google-chrome

    Google Chrome Frame is an early-stage open source plug-in that seamlessly brings Google Chrome's open web technologies and speedy JavaScript engine to Internet Explorer. With Google Chrome Frame, you can:

    • Start using open web technologies - like the HTML5 canvas tag - right away, even technologies that aren't yet supported in Internet Explorer 6, 7, or 8.
    • Take advantage of JavaScript performance improvements to make your apps faster and more responsive.

    What is even more clever is that thanks to a special embedded tags in your html body, you can propose to your visitor to install this plugin, and thus increase market share of Google chrome. That’s a direct hit at Microsoft domination plans :-) (we own the file format, and runtime environment)

    &160;

    <body>
    <script type="text/javascript" 
    src="http://ajax.googleapis.com/ajax/libs/chrome-frame/1/CFInstall.min.js"> </script>
     
    <div id="placeholder"></div>
    
    <script>
     CFInstall.check({
        node: "placeholder",
        destination: "http://www.waikiki.com"
      });
    </script>
    </body>

    Adding this tag in <head> section of your blog is for users running Internet Explorer with Google Chrome Frame installed. This will automatically render yours pages with Google Chrome Frame instead of IE.

     <meta http-equiv="X-UA-Compatible" content="chrome=1">

    After that, you can visit any site and render it with Google frame by appending cf: to any http:// url’s,

    cf:http://www.waltercedric.com/

    Personally I will stick to Firefox/Chrome/Opera and use them when it make sense.

    &160;

    google.chrome.frame

    Developer guide at http://code.google.com/chrome/chromeframe/developers_guide.html

    Download&160; at http://code.google.com/chrome/chromeframe/