tree: 94b5e64e4e9455733359cd1607aec72ae7c7eb3b [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. file_manager/
  9. files_internals/
  10. firmware_update_ui/
  11. help_app_ui/
  12. media_app_ui/
  13. multidevice_debug/
  14. network_ui/
  15. os_feedback_ui/
  16. personalization_app/
  17. print_management/
  18. print_preview_cros/
  19. projector_app/
  20. resources/
  21. sample_system_web_app_ui/
  22. scanning/
  23. settings/
  24. shimless_rma/
  25. shortcut_customization_ui/
  26. status_area_internals/
  27. system_apps/
  28. tools/
  29. vc_background_ui/
  30. web_applications/
  31. .eslintrc.js
  32. ash_webui_test_suite.cc
  33. ash_webui_test_suite.h
  34. BUILD.gn
  35. DEPS
  36. OWNERS
  37. PLATFORM_OWNERS
  38. PRESUBMIT.py
  39. README.md
  40. 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.