Page MenuHomePhabricator

Automatically build mobile menus from navigation, and clean up external ProfileMenu API
ClosedPublic

Authored by epriestley on Mar 31 2019, 6:54 PM.
Tags
None
Referenced Files
F18849792: D20356.id48607.diff
Thu, Oct 30, 12:19 PM
F18837141: D20356.diff
Mon, Oct 27, 4:32 AM
F18823115: D20356.id.diff
Thu, Oct 23, 10:14 AM
F18821944: D20356.diff
Thu, Oct 23, 2:59 AM
F18770730: D20356.id48607.diff
Wed, Oct 8, 2:28 PM
F18756182: D20356.id48574.diff
Sun, Oct 5, 9:55 AM
F18755088: D20356.id48607.diff
Sun, Oct 5, 3:36 AM
F18653928: D20356.diff
Sep 21 2025, 10:35 PM
Subscribers
None

Details

Summary

Depends on D20355. Ref T13275. Ref T13247. Currently, "Hamburger" menus are not automatically built from navigation menus. However, this is (I'm almost completely sure?) a reasonable and appropriate default behavior, and saves us some code around profile menus.

With this rule in place, we can remove setApplicationMenu() and getApplicationMenu() from StandardPageView, since they have no callers.

This also updates a lot of profile menu callsites to a new API which is added in the next change.

Test Plan

See the next two changes.

Diff Detail

Repository
rP Phabricator
Branch
portal6
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 22447
Build 30723: Run Core Tests
Build 30722: arc lint + arc unit