File: README.md

package info (click to toggle)
chromium 139.0.7258.138-1
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 6,120,676 kB
  • sloc: cpp: 35,100,869; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (28 lines) | stat: -rw-r--r-- 1,031 bytes parent folder | download | duplicates (8) 
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
 
## Extensions Dialogs

### Steps for creating a new dialog

1. If the dialog is called from code outside views, which most likely is, add
`Show<Name>Dialog` method to `chrome/browser/ui/extensions/extensions_dialogs.h`
2. Implement `Show<NameDialog` in `chrome/browser/ui/views/extensions`:

- Method should receive all the information to display in the UI, and should not compute any extensions logic (e.g pass `extension_site_access` value instead of computing the site access here).
- Use `ui::DialogModel::Builder` to create the dialog. See more information on
 `ui/base/models/dialog_model.h`
- Show the dialog using a util method from `chrome/browser/ui/views/extensions/extensions_dialogs_utils.h`

```
namespace extensions {

void Show<Name>Dialog(...) {
  ui::DialogModel::Builder
    .SetTitle(...)
    // Set the dialog information. If necessary, use ui::DialogModelDelegate.

  ShowDialog(...)
}

}  // namespace
```

3. Add interactive tests using Kombucha. See more information on `chrome/test/interaction/README.md`