| OLD | NEW |
|---|
| (Empty) |
| 1 # Actions. | |
| 2 | |
| 3 ----- | |
| 4 **The files in this directory are only used in the new iOS Chrome | |
| 5 architecture.** | |
| 6 ----- | |
| 7 | |
| 8 This directory contains header files that define action protocols. Functionally | |
| 9 these protocols are used to add application-specific methods to `UIResponder`, | |
| 10 to allow controls to send action messages up the responder chain. | |
| 11 | |
| 12 These protocols headers are in this directory because, although they relate to | |
| 13 specific UI features (settings, toolbar, etc), they will be used by different | |
| 14 UI components, and should be independent of any specific UI implementation. | |
| 15 | |
| 16 Classes that instantiate controls that *send* the methods in one of these | |
| 17 protocols will need to import the header for that protocol, but won't need to | |
| 18 conform to it. | |
| 19 | |
| 20 Classes in the responder chain that *handle* any of these methods need to | |
| 21 conform to the protocol. | |
| 22 | |
| 23 These protocols are specifically for use in the UI-layer target/action context, | |
| 24 and shouldn't be used for other purposes. The `sender` parameter of any of these | |
| 25 methods should always be an actual `UIControl` instance that the user is | |
| 26 interacting with. | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2592983003:
[Clean Skeleton] Migrate code to clean/ (Closed)
