File: README.md

package info (click to toggle)
chromium 138.0.7204.183-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 6,080,960 kB
  • sloc: cpp: 34,937,079; ansic: 7,176,967; javascript: 4,110,704; python: 1,419,954; 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,811; 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 (14 lines) | stat: -rw-r--r-- 713 bytes parent folder | download | duplicates (5) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
 
The sensitive content component is responsible for detecting form content that
should be marked as "sensitive" on Android V+ (e.g., payment information, login
information). It is used by both Chrome and WebView on Android.

If a view is marked as sensitive, and the API level is at least 35, the OS will
redact the view during screen sharing, screen recording, and similar actions.

The `SensitiveContentClient` is used for dependency injection from the embedder.
The client communicates with the embedder, in order to mark/unmark the content
as being sensitive.

The `SensitiveContentManager` is owned by the client. It contains
platform-independent logic and tracks whether sensitive fields are present or
not.