tree: a7220e624a39748c12f4e2d8f368f639d45c0b3e [path history] [tgz]
  1. camera_app_ui/
  2. color_internals/
  3. common/
  4. connectivity_diagnostics/
  5. demo_mode_app_ui/
  6. diagnostics_ui/
  7. eche_app_ui/
  8. face_ml_app_ui/
  9. file_manager/
  10. firmware_update_ui/
  11. guest_os_installer/
  12. help_app_ui/
  13. media_app_ui/
  14. multidevice_debug/
  15. network_ui/
  16. os_feedback_ui/
  17. personalization_app/
  18. print_management/
  19. projector_app/
  20. resources/
  21. sample_system_web_app_ui/
  22. scanning/
  23. shimless_rma/
  24. shortcut_customization_ui/
  25. system_apps/
  26. system_extensions_internals_ui/
  27. telemetry_extension_ui/
  28. web_applications/
  29. .eslintrc.js
  30. ash_webui_test_suite.cc
  31. ash_webui_test_suite.h
  32. BUILD.gn
  33. DEPS
  34. OWNERS
  35. PLATFORM_OWNERS
  36. PRESUBMIT.py
  37. README.md
  38. 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.