Settings Router Refactor: Remove route.page legacy property.

chrome/browser/resources/settings/settings_page/settings_router.js

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 /**
  * @fileoverview
  * 'settings-router' is a simple router for settings. Its responsibilities:
  *  - Update the URL when the routing state changes.
  *  - Initialize the routing state with the initial URL.
  *  - Process and validate all routing state changes.
  *
  * Example:
  *
  *    <settings-router current-route="{{currentRoute}}">
  *    </settings-router>
  */
 Polymer({
   is: 'settings-router',
 
   properties: {
     /**
      * The current active route. This may only be updated via the global
      * function settings.navigateTo.
      *
-     * currentRoute.page refers to top-level pages such as Basic and Advanced.
-     *
      * currentRoute.section is only non-empty when the user is on a subpage. If
      * the user is on Basic, for instance, this is an empty string.
      *
      * currentRoute.subpage is an Array. The last element is the actual subpage
      * the user is on. The previous elements are the ancestor subpages. This
      * enables support for multiple paths to the same subpage. This is used by
      * both the Back button and the Breadcrumb to determine ancestor subpages.
      * @type {!settings.Route}
      */
     currentRoute: {
@@ skipping 29 matching lines @@
   navigateTo_: function(route) {
     assert(!!route);
 
     if (route == this.currentRoute)
       return;
 
     window.history.pushState(undefined, document.title, route.path);
     this.currentRoute = route;
   },
 });