commit | e08093dc66512c3b822d9a3b072ca6a6bcb4cfe2 | [log] [tgz] |
---|---|---|
author | Avi Drissman <avi@chromium.org> | Mon Mar 17 01:50:41 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 17 01:50:41 2025 |
tree | c8d6d76b8db5166442c6f22753afb584105cf097 | |
parent | b74b0b68ffc09b5c94297fcc05fa0cd8d055db69 [diff] |
Do popup modernization without switching to the new API https://crrev.com/c/6173642 switched to new API for doing popup menus, but it also did some associated cleanup. While the new API was buggy (see https://crbug.com/401443090) and therefore had to be reverted, the cleanup aspects are still a good idea, so re-land them. Specifically: - Switching WebMenuRunner to have explicit testing callbacks rather than requiring other code to swizzle NSView with the knowledge of the WebMenuRunner internals. - Removal of the "useWithPopUpButtonCell" parameter on MenuControllerCocoa, which was not actually used for PopUpButtonCells! (The WebMenuRunner builds its own menus.) - Removal of the default -init on MenuControllerCocoa due to having no callers; now MenuControllerCocoa always eagerly builds the menu, simplifying things. - Light code modernization. Bug: 389067059 Include-Ci-Only-Tests: chromium.mac:mac14-tests|browser_tests Change-Id: If62fd54001c9ad2c50e6bd96a97c894b00a7bc61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6351721 Commit-Queue: Avi Drissman <avi@chromium.org> Reviewed-by: Keren Zhu <kerenzhu@chromium.org> Reviewed-by: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/main@{#1433321}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.