File: README.chromium

package info (click to toggle)
chromium 138.0.7204.183-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 6,071,908 kB
  • sloc: cpp: 34,937,088; ansic: 7,176,967; javascript: 4,110,704; python: 1,419,953; asm: 946,768; xml: 739,971; pascal: 187,324; sh: 89,623; perl: 88,663; objc: 79,944; sql: 50,304; cs: 41,786; fortran: 24,137; makefile: 21,806; php: 13,980; tcl: 13,166; yacc: 8,925; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (54 lines) | stat: -rw-r--r-- 1,621 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
This directory contains accessibility extensions developed by the
Chrome team, not included with Chrome by default, but available via a
one-click install from the Settings page.

#
# Building
#

Some of the extensions have localized strings and need to be built:

ninja -C out/Release ui/accessibility/extensions:extensions

The built extensions will be in your out directory, e.g.:

out/Release/colorehancer

All other extensions should be zipped and uploaded to the webstore.

Note for chromevoxclassic:
see chromevoxclassic/README for further details.

You can build all extension tests by doing:

ninja -C out/Release ui/accessibility/extensions:extension_tests

This currently produces tests for ChromeVox Classic, Color Enhancer,
and Caret Browsing.

out/Release/chromevox_tests
out/Release/colorenhancer_tests
out/Release/caretbrowsing_tests

These targets are not run on a bot, so run the relevant tests manually
before release!

#
# Instructions for publishing to the web store (new as of August 2019):
#

Googlers, you need to be a member of the chrome-a11y-extensions group:
https://groups.google.com/a/google.com/d/forum/chrome-a11y-extensions

Then visit the Chrome Web Store and you can manage the extension. Remember to
increment the version of each extension every time you update it.

#
# Script
#

This script can be used to programmatically update extensions. Proceed with caution,
only use this if you are already comfortable updating an extension manually, you have a
rollback plan, and you can take the time to understand the script.

ui/accessibility/extensions/tools/publish_webstore_extension.py