サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
ノーベル賞
www.chromium.org
Chrome 20 and later implements a mechanism that is intended to prevent distributed denial of service (DDoS) attacks from being perpetrated, maliciously or accidentally, by extensions running within Chrome. Chrome 12 through 19 had a different flavor of this feature, see here. To disable the feature, which may be useful for some extension developers: Pass the --disable-extensions-http-throttling co
Proposal As browser users manage more and more of their day-to-day lives online, we (Chrome Security) believe they should reasonably expect that browsing and interacting with the web is secure and protects their sensitive information across their entire browsing experience. Protecting users’ privacy and security requires connecting to secure origins wherever possible. Practically speaking, this me
Build the QUIC client and server A sample server and client implementation are provided in Chromium, and several more are provided as part of QUICHE. To use these you should first have checked out the Chromium source, and then build the binaries: ninja -C out/Debug quic_server quic_client Binary targets include: quic_server - a QUIC server for testing purposes defined in //net/tools/quic/quic_simp
Overview The USB Type-C to HDMI Adapter connects a USB Type-C plug to an HDMI receptacle. It enables users of any Chrome device that implements USB-Type C to connect to an HDMI display. Hardware Capabilities This adapter is an implementation of a USB Type-C DFP_D to HDMI Protocol Converter. It follows the requirements of section 4.3.1 of the VESA DisplayPort Alt Mode for USB Type-C Standard. In th
Introduction The Chromebooks with Intel processors are fast. I've replaced my Macbook Air with a Chromebook, and run the standard Chrome OS software on VT01, and virtual machines on VT02. I have booted both Windows and different versions of Linux and the 9front version of Plan 9. I currently use a custom build of Qemu. It's a bit hard to get Qemu built in the Chrome OS build system at present, so
This page contains the original proposal for marking HTTP as non-secure (see Original Proposal below). Since then, the Chrome usable security team has announced the following phases towards this goal. For more information see, the WebFundamentals article: Avoiding the Not Secure Warning in Chrome Timeline January 2017 (Phase 1) Takes effect: January 2017 (Chrome 56) Announcement: Moving towards a
Introduction This page contains information about the Asus Chromebox that is interesting and/or useful to software developers. For general information about getting started with developing on Chromium OS (the open-source version of the software on the Chrome Notebook), see the Chromium OS Developer Guide. Specifications CPU: Haswell Celeron 2995U. 1.4GHz, dual-core, 2MB Cache OR 1.7 GHz Core i3-40
The following is deprecated and left for historical purposes. Please see the editor's draft of the spec for the most up to date design: https://w3c.github.io/webappsec-suborigins/ Objective Our objective is to provide a new mechanism for allowing sites to easily separate their content into separate, flexible synthetic origins while serving content from a single physical origin. Furthermore, the sy
Last updated: 2024-01-16 Bookmark this page as https://g.co/chrome/root-policy Table of Contents Introduction Apply for Inclusion Moving Forward, Together Additional Information Change History Minimum Requirements for CAs 1. Baseline Requirements 2. Chrome Root Program Participant Policies 3. Modern Infrastructures 4. Dedicated TLS Server Authentication PKI Hierarchies 5. Audits 6. Annual Self-ass
Slimming Paint is a Paint team project to re-implement the Blink<->cc picture recording API to work in terms of a global display list rather than a tree of cc::Layers (~aka GraphicsLayer in Blink terminology). It will result in a drastic simplification of the way that composited layers are represented in Blink and cc, which in turn will yield improved performance, correctness and flexibility. To g
QUIC is a new multiplexed transport built on top of UDP. HTTP/3 is designed to take advantage of QUIC's features, including lack of Head-Of-Line blocking between streams. The QUIC project started as an alternative to TCP+TLS+HTTP/2, with the goal of improving user experience, particularly page load times. The QUIC working group at the IETF defined a clear boundary between the transport(QUIC) and a
Q: How do I debug? A: From a page on the same origin, go to Developer Tools > Application > Service Workers. You can also use chrome://inspect/#service-workers to find all running service workers. To poke around at the internals (usually only Chromium developers should need this), visit chrome://serviceworker-internals . Q: When I have Developer Tools open, requests go straight to the network; the
This documentation moved to the repository at https://chromium.googlesource.com/chromium/src/+/HEAD/content/README.md (except for the diagram below). The diagram above illustrates the layering of the different modules. A module can include code directly from lower modules. However, a module can not include code from a module that is higher than it. This is enforced through DEPS rules. Modules can
NOTE: THIS DOCUMENT IS NO LONGER VALID It is left available out of historical interest. Overview Blink-in-JavaScript is a mechanism to enable Blink developers to implement DOM features in JavaScript (instead of C++). The goal of Blink-in-JS is to improve web layering by implementing high-level DOM features on top of existing web-exposed APIs. You can learn the design in this design document and th
For Web Developers What is service worker? See the service worker documentation at Mozilla Developer Network. Debugging Working with a service worker is a little different than normal debugging. Check out Service Worker Debugging for details. Track Status Service workers shipped in Chrome 40 (which was promoted to stable channel in January 2015). Is Service Worker Ready? tracks the implementation
What is this doc? If there are features which use Google APIs that you need for a custom build, fork, or integration of stock Chromium. If you are building ChromiumOS yourself, as API access is required for login. Note: Software distribution with keys acquired for yourself is allowed, but the keys themselves cannot be shared with parties outside the legal entity that accepted the API ToS. Keep in
Overview For developers of Chromium OS there are many helpful packages included as part of developer and test images that are not included as part of Chrome OS. Bootstrapping and getting these back into the system can be very difficult without re-imaging the entire device. Ideally, you'd be able to get these packages back but still auto-update the rest of the system. Dev-install solves this use ca
Objective One of the goals for the launch of Chromium is to support 40 UI languages; that is, the UI needs to be localized for each language such that any UI text element (menus, titles, labels, etc.) is displayed in the target language. In order to make sure that Chromium can be easily localized to different languages (an effort known as localizability), the Chromium source code is structured suc
When diagnosing performance problems it can be valuable to see what Chrome is doing "under the hood." One way to get a more detailed view into what's going on is to use the about:tracing tool. Tracing records activity in Chrome's processes (see multi-process architecture for more on what each process is doing). It records C++ or javascript method signatures in a hierarchical view for each thread i
Application level Use a single connection - it’s better for SPDY performance and for the internet to use as few connections as possible. For SPDY, this will result in better packing of data into packets, better header compression, less connection state, fewer handshakes, etc. It improves TCP behavior across the internet and reduces bufferbloat. Interacts better with NATs as well as it requires les
We recently updated our plans to phase out support for NPAPI in early 2015. This guide provides more details about what to expect and alternatives to NPAPI. Timeline January 2014 Starting in Chrome 32*—expected to reach the Stable channel in mid-January 2014—*when a user visits a page with a blocked NPAPI plug-in, they will see: Note that users who have already installed the plug-in in previous ve
Introduction This page contains information about the Acer C720 Chromebook and Acer C720P Chromebook and Acer C740 Chromebook that is interesting and/or useful to software developers. For general information about getting started with developing on Chromium OS (the open-source version of the software on the Chrome Notebook), see the Chromium OS Developer Guide. Specifications CPU: Haswell Celeron
Everything you need to know about audio/video inside Chromium and Chromium OS! Whom To Contact It's best to have discussions on chromium-dev@chromium.org or media-dev@chromium.org for media specific matters. We are component Internals>Media on the Chromium bug tracker. Documentation See media/README.md. For historical reference, here's the original design doc for HTML5 audio/video. Codec and Conta
The Chromium graphics stack is complicated, and has been evolving rapidly for the last several years. As a result of this rapid evolution, plus the pressure to try to ship performance-improving features as fast as possible, we’ve developed a large matrix of feature configurations on different platforms. This document lays out what’s enabled where, as well as our long-term plans for the architectur
There are command-line switches that Chromium (and Chrome) accept in order to enable particular features or modify otherwise default functionality. There is no list of all switches, but most of the existing switches can be found at https://peter.sh/examples/?/chromium-switches.html. Note: Chrome switches (e.g., --incognito) and Chrome flags (e.g., chrome://flags/#ignore-gpu-blocklist) are separate
Public Documentation If you want to build a PNaCl application for Chrome, start with the Native Client developer documentation Introduction Native Client (NaCl) is a secure sandbox for running untrusted native machine code in the Chrome browser. NaCl programs have special restrictions on the generated code, which are implemented by the compiler toolchain and statically verified at runtime by the t
次のページ
このページを最初にブックマークしてみませんか?
『The Chromium Projects』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く