tree: 7c6738e307c71a62ed6981559bef818c136b5ea2 [path history] [tgz]
  1. camera_app_ui/
  2. common/
  3. connectivity_diagnostics/
  4. demo_mode_app_ui/
  5. diagnostics_ui/
  6. eche_app_ui/
  7. file_manager/
  8. firmware_update_ui/
  9. help_app_ui/
  10. media_app_ui/
  11. network_ui/
  12. os_feedback_ui/
  13. personalization_app/
  14. print_management/
  15. projector_app/
  16. resources/
  17. sample_system_web_app_ui/
  18. scanning/
  19. shimless_rma/
  20. shortcut_customization_ui/
  21. system_apps/
  22. system_extensions_internals_ui/
  23. telemetry_extension_ui/
  24. web_applications/
  25. ash_webui_test_suite.cc
  26. ash_webui_test_suite.h
  27. BUILD.gn
  28. DEPS
  29. OWNERS
  30. PRESUBMIT.py
  31. README.md
  32. run_all_unittests.cc
ash/webui/README.md

//ash/webui

//ash/webui contains code that is Chrome OS-specific WebUI for system web apps and has dependencies on //content.

General purpose window manager or system UI code should not have content dependencies, and should not live in this directory. Prefer a different top-level ash directory, like //ash/system, //ash/wm, or add //ash/your_feature. Low-level components go in //ash/components/your_feature.

Each subdirectory should be its own separate “module”, and have its own BUILD.gn file. See this directory's BUILD.gn file for tips on adding your own subdirectory.

This directory is in //ash because it runs in the “ash-chrome” binary when Lacros is running. Most of its subdirectories used to live in //chromeos/components. See the Lacros documentation or the Lacros directory migration design.