サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
Appleイベント
chromium.googlesource.com
A Guide for Code ReviewersFor the code author counterpart, see Respectful Changes. Assume competence & goodwillWe attract competent people - and that means even when they‘re wrong, it most likely comes from lack of information, not from inability. A “bad” CL usually means one of the parties is in possession of information the other one isn’t aware of. Discuss in personIf there is a disagreement, h
Warning: This document is old & has moved. Please update any links: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/constants/syscalls.md These are the system call numbers (NR) and their corresponding symbolic names. These vary significantly across architectures/ABIs, both in mappings and in actual name. This is a quick reference for people debugging things (e.g. seccomp failures). For mo
9dd38de fix clang/-Wcast-function-type-strict warning by James Zern · 3 weeks ago main653745a Lower GetExpectedDistortion() for near-lossless by Yannis Guyon · 5 weeks agod08031d Migrate fuzz_image_and_dec_config to FuzzTest by Yannis Guyon · 5 weeks ago95dd75e Use config in fuzz TestImageDecConfig() by Yannis Guyon · 5 weeks ago543e052 Implement operator= && by Vincent Rabaud · 6 weeks ago WebP 2
A large change was made to the way Chrome records underlying layout shifts which contribute to Cumulative Layout Shift in Chrome 86. The source code of the change is here. The goal of the change was to better align the implementation to the specification, which says: The visual representation of a Node N is defined as follows: If N is an Element which generates one or more boxes, the visual repres
// Use of this source code is governed by a BSD-style license that can be
This document establishes basic proxy terminology and describes Chrome-specific proxy behaviors. Proxy server identifiersA proxy server is an intermediary used for network requests. A proxy server can be described by its address, along with the proxy scheme that should be used to communicate with it. This can be written as a string using either the “PAC format” or the “URI format”. The PAC format
Enforce 398-day validity for certificates issued on-or-after 2020-09-01 Enforce publicly trusted TLS server certificates have a lifetime of 398 days or less, if they are issued on or after 2020-09-01. Certificates that violate this will be rejected with ERR_CERT_VALIDITY_TOO_LONG and will be treated as misissued. Bug: 1097982 Change-Id: I0fdccd93cc9fd0ee1011b37be7b584a8ce6653d9 Reviewed-on: https:
Download the VMcd to your Chromium repository, and enter the Simple Chrome SDK environment with --download-vm: (shell) .../chrome/src $ cros chrome-sdk --board=amd64-generic \ --download-vm --clear-sdk-cache --log-level=info chrome-sdk options--download-vm downloads a pre-packaged VM and QEMU (takes a few minutes).--clear-sdk-cache recommended, clears the cache.--log-level=debug for additional out
Why this is importantOur Code of Conduct under “Be respectful and constructive” says: Each of us has the right to enjoy our experience and participate without fear of harassment, discrimination, or condescension, whether blatant or subtle. Emphasis is added: unnecessarily exclusive code is discriminatory and condescending, and reading biased code isn't enjoyable. Gender-NeutralSome points in our c
This document explains a high-level design of PartitionAlloc. If you're interested in its in-depth implementation, see comments in PartitionAlloc.h. OverviewPartitionAlloc is a memory allocator optimized for performance and security in Blink. All objects in Blink are expected to be allocated with PartitionAlloc or Oilpan (but not yet done). Partitions and bucketsPartitionAlloc has four partitions.
Google and the Chromium team are committed to preserving and fostering a diverse, welcoming community. Below is our community code of conduct, which applies to our repos and organizations, issue trackers, mailing lists, blog content, and any other Chromium-supported communication group, as well as any private communication initiated in the context of these spaces. This code of conduct must be foll
Get started here. Visual Studio Code (VS Code) is a free, open source, lightweight and powerful code editor for Windows, macOS and Linux, based on Electron/Chromium. It has built-in support for JavaScript, TypeScript and Node.js and a rich extension ecosystem that adds intellisense, debugging, syntax highlighting etc. For many languages like C++, Python, Go, Java, it works without too much setup.
Use of this useless file is governed by a BSD-style license that can be
When you write code to parse, evaluate, or otherwise handle untrustworthy inputs from the Internet — which is almost everything we do in a web browser! — we like to follow a simple rule to make sure it's safe enough to do so. The Rule Of 2 is: Pick no more than 2 of untrustworthy inputs;unsafe implementation language; andhigh privilege. (drawing source here) Why?When code that handles untrustworth
Warning: This document is old & has moved. Please update any links: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/glossary.md 3PL: Third Party Labs.ACLs: Access Control Lists.AFE: Auto Test Front End.AP: Application Processor.AU: Auto Updates.AVL: Approved Vendor List.BCS: Binary Component Server.BFT: Board Function Testing.BOM: Bill of Materials.BSP: Board support package.BVT: Build &
OverviewSecurity is one of the most important goals for Chromium. The key to security is understanding: we can only truly secure a system if we fully understand its behaviors with respect to the combination of all possible inputs in all possible states. For a codebase as large and diverse as Chromium, reasoning about the combined behavior of all its parts is nearly impossible. The sandbox objectiv
This document covers the best practices and pitfalls for building UI to display URLs in browsers and other apps. It covers the main categories of problems and challenges that we’ve seen in building Chrome. The guidance is intended to be generally applicable, but includes some Chrome-specific notes throughout. BackgroundThe URL displayed in a user agent's address bar is often the only security cont
Warning: This document is old & has moved. Please update any links: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/containers_and_vms.md Welcome to the containers project where we support running arbitrary code inside of VMs in Chrome OS. This is a heavily-technical document; for user-friendly information, see The Keyword & Set up Linux (Beta) on your Chromebook documentation. If you're
This document outlines Cross-Origin Read Blocking (CORB), an algorithm by which dubious cross-origin resource loads may be identified and blocked by web browsers before they reach the web page. CORB reduces the risk of leaking sensitive data by keeping it further from cross-origin web pages. In most browsers, it keeps such data out of untrusted script execution contexts. In browsers with Site Isol
Android container in Chrome OSThis document outlines the process by which Android runs in a Linux container in Chrome OS. This document explains how the container for Android master works unless otherwise noted. The container for N may work in a slightly different way. config.jsonconfig.json is used by run_oci, to describe how the container is set up. This file describes the mount structure, names
ed7d455 Switch main crosvm repo by Dennis Kempin · 1 year, 4 months ago factory-foobar-15000.B-main main release-R105-14989.B-main stabilize-14998.B-main3ebfc9b audio: Support null backend for VirtioSnd by Norman Bintang · 1 year, 5 months ago8f9de92 crosvm: make JailConfig structure parseable from command-line options by Alexandre Courbot · 1 year, 5 months agoa0bf956 tools: build example_simple
IntroductionThe user data directory contains profile data such as history, bookmarks, and cookies, as well as other per-installation local state. Each profile is a subdirectory (often Default) within the user data directory. Current LocationTo determine the user data directory for a running Chrome instance: Navigate to chrome://versionLook for the Profile Path field. This gives the path to the pro
Warning: This document is old & has moved. Please update any links: https://chromium.googlesource.com/apps/libapps/+/HEAD/nassh/docs/FAQ.md .--~~~~~~~~~~~~~------. /--===============------\ | |```````````````| | | | | | | | >_< | | | | | | | |_______________| | | ::::| '=======================' //-"-"-"-"-"-"-"-"-"-"-\\ //_"_"_"_"_"_"_"_"_"_"_"_\\ [-------------------------] \_____________________
Add support for Animated PNG Update the browser accept header to state that APNG is supported. Split the decoding of PNG images into two stages: parsing and decoding. During parsing, chunks are handled one of three ways: - acTL and fcTL chunks, which specify properties of an APNG are read and the properties are stored. If they contain an error before IDAT, the image is treated as a static PNG, as
Headless Chromium allows running Chromium in a headless/server environment. Expected use cases include loading web pages, extracting metadata (e.g., the DOM) and generating bitmaps from page contents -- using all the modern web platform features provided by Chromium and Blink. There are two ways to use Headless Chromium: Usage via the DevTools remote debugging protocolStart a normal Chrome binary
NOTE: Please update your link to this file! The new file location is //docs/ios/build_instructions.md
This directory holds code related to Chrome for iOS. See this document for a description of the structure underneath this directory.
次のページ
このページを最初にブックマークしてみませんか?
『chromium Git repositories - Git at Google』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く