tree: 505b8c7dfb88e033b39c3aac244fa9544cc61bbb [path history] [tgz]
  1. chromeos/
  2. DIR_METADATA
  3. OWNERS
  4. README.md
  5. extensions.gni
third_party/blink/renderer/extensions/README.md

The extensions/ directory

The extensions/ directory contains embedder-specific, not-web-exposed APIs (e.g., not-web-exposed APIs for Chromium OS etc). The directory is useful to implement embedder-specific, not-web-exposed APIs using Blink technologies for web-exposed APIs like WebIDL, V8 bindings and Oilpan.

Remember that you should not implement any web-exposed APIs in extensions/. Web-exposed APIs should go through the standardization process and be implemented in core/ or modules/. Also, per the Chromium contributor guideline, code that is not used by Chromium should not be added to extensions/.

In terms of dependencies, extensions/ can depend on modules/, core/ and platform/, but not vice versa.

The extensions/ directory contains sub-directories for individual embedders (e.g., extensions/chromeos/). Each sub-directory is linked into the Blink link unit only when the embedder is built.