A linear search is performed at https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/resources/settings/settings_page/settings_router.js&l=42-51 to find which page to display based on the current URL.
This does not seem very scale-able as we start exposing more URLs that navigate to specific sub sections of the settings. Currently there are 46 routes.
A possible alternative would be instead of using an array to hold all possible routes, to use a tree data structure which represents the page-subpage-subsection structure. The page to display can be found by simply navigating the tree based on the current URL.
I really don't care about the efficiency of looking through 40 extra property lookups unless you can prove it's slow. But we need to support dialogs in URLs (i.e. /clearBrowserData) so I'll re-purpose your bug.
Comment 1 by tbuck...@chromium.org
, May 2 2016