Comment 3 for bug 1491934

My understanding is that the current web-app navigation UI was intended to be aligned as closely as possible with the browser:
(https://docs.google.com/presentation/d/1IpCWtWuGPES5llwmoscawhn2IG4fxOggMO8F_RM_zms/edit)

Using radial menus on the bottom edge has the potential to introduce its own disadvantages, so may not be a 'quick-fix' to this;
- the introduction of additional steps to navigating (the first of which is an edge-gesture)
- making navigation less immediately discoverable
- discouraging the use of the bottom-edge by developers for anything else if the expectation becomes 'that's where navigation occurs' (when we typically encourage that the bottom-edge be used for the most critical/interesting/exciting action available)
- etc.

Could you provide the reports you mentioned and/ or some illustration (e.g. screenshots) of the problem you're describing to help us understand the issue? The hide/ reveal Navigation UI pattern that is used by web-apps has long been present in the browser, scopes, contacts & telephony, etc - Just about anything with a 'header' (see comparative screenshots below).