Google Git
Sign in
chromium / chromium / src / lkgr / . / ui / views / cocoa
tree: 3965a3f8a7337c46212d9a94910912945bb26396 [path history] [tgz]
  1. bridged_native_widget_interactive_uitest.mm
  2. bridged_native_widget_unittest.mm
  3. cocoa_mouse_capture_unittest.mm
  4. DEPS
  5. drag_drop_client_mac.h
  6. drag_drop_client_mac.mm
  7. drag_drop_client_mac_unittest.mm
  8. fullscreen_controller_unittest.cc
  9. immersive_mode_controller_unittest.mm
  10. immersive_mode_reveal_client.h
  11. native_widget_mac_event_monitor.h
  12. native_widget_mac_event_monitor.mm
  13. native_widget_mac_ns_window_host.h
  14. native_widget_mac_ns_window_host.mm
  15. native_window_tracker_cocoa.h
  16. native_window_tracker_cocoa.mm
  17. OWNERS
  18. README.md
  19. text_input_host.h
  20. text_input_host.mm
  21. tooltip_manager_mac.h
  22. tooltip_manager_mac.mm
ui/views/cocoa/README.md

This directory contains odds and ends that directly interface between Cocoa, the native macOS UI toolkit and Chrome's Views toolkit.

If you're looking for the bigger picture of how Cocoa and Views interact, you are looking for Remote Cocoa, the system that bridges Cocoa objects like NSWindows and NSViews with their Views counterparts either in-process (the browser) or out-of-process (PWA app shims). The Remote MacViews Overview is a good place to start and components/remote_cocoa is the best place to start code exploration.