[MD History] Add routing to the synced devices page.

[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.linux:closure_compilation

Committed: https://crrev.com/357edd888ea83097acfec6125c6cb478d2499d03
Cr-Commit-Position: refs/heads/master@{#406488}

[calamity, 2016-06-07 05:38:06]

Description was changed from

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
==========

to

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation
==========

[calamity, 2016-06-07 07:59:31]

Description was changed from

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation
==========

to

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation
==========

[calamity, 2016-06-07 08:03:00]

calamity@chromium.org changed reviewers:
+ tsergeant@chromium.org

[tsergeant, 2016-06-08 03:42:18]

Take my suggestions with a grain of salt, since I'm mostly going off the basics
of the Shop code and a quick look at the app-route docs.

Also, I wasn't able to get this working locally, see the comment in app.html.

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
File chrome/browser/resources/md_history/app.html (right):

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.html:10: <link rel="import"
href="chrome://resources/polymer/v1_0/app-route/app-location.html">
Nit: Sort imports

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.html:60: <history-side-bar
id="history-side-bar" selected-page="{{selectedPage}}"
The history-app property is called `selectedPage_`, not `selectedPage`, which
seems to be stopping this from working for me.

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.html:61: route-data="{{routeData}}">`
There's a sneaky ` character hiding out here.

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
File chrome/browser/resources/md_history/app.js (right):

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.js:86: };
I'm not a big fan of this (as I think you predicted). What you're creating is a
1-1 mapping between two different types of strings, with a default:

openTabs <-> history-synced-device-manager
* --> history-list

Why not just use the string on the left (the user friendly page name)
everywhere, rather than using the string on the right in some places?

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
File chrome/browser/resources/md_history/side_bar.html (right):

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/side_bar.html:45: <paper-listbox id="menu"
selected="[[routeData.page]]"
Should this be 2-way bound?

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/side_bar.html:48: <paper-item
view-id="history-list" class="page-item" path="">
This element has a bunch of extra logic to work with the awkwardness around
selectedPage vs route.

You might be able to simplify this logic a bunch by using <a> tags. Then the
flow becomes:

click <a> -> app-route updates -> selected page updates -> sidebar selection
updates.

We would also get the other benefits of <a> tags like being able to middle
click.

https://codereview.chromium.org/2042973002/diff/20001/ui/webui/resources/poly...
File ui/webui/resources/polymer_resources.grdp (right):

https://codereview.chromium.org/2042973002/diff/20001/ui/webui/resources/poly...
ui/webui/resources/polymer_resources.grdp:23: <structure
name="IDR_POLYMER_1_0_APP_ROUTE_APP_LOCATION_EXTRACTED_JS"
You can remove app-route from third_party/polymer/v1_0/find_unused_elements.py

[calamity, 2016-06-14 05:05:50]

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
File chrome/browser/resources/md_history/app.html (right):

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.html:10: <link rel="import"
href="chrome://resources/polymer/v1_0/app-route/app-location.html">
On 2016/06/08 03:42:17, tsergeant wrote:
> Nit: Sort imports

Done.

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.html:60: <history-side-bar
id="history-side-bar" selected-page="{{selectedPage}}"
On 2016/06/08 03:42:17, tsergeant wrote:
> The history-app property is called `selectedPage_`, not `selectedPage`, which
> seems to be stopping this from working for me.

Done.

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.html:61: route-data="{{routeData}}">`
On 2016/06/08 03:42:17, tsergeant wrote:
> There's a sneaky ` character hiding out here.

Done.

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
File chrome/browser/resources/md_history/app.js (right):

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/app.js:86: };
On 2016/06/08 03:42:17, tsergeant wrote:
> I'm not a big fan of this (as I think you predicted). What you're creating is
a
> 1-1 mapping between two different types of strings, with a default:
> 
> openTabs <-> history-synced-device-manager
> * --> history-list
> 
> Why not just use the string on the left (the user friendly page name)
> everywhere, rather than using the string on the right in some places?

Ok, so we'll be going with /, /grouped/week, /grouped/month, /openTabs I guess?

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
File chrome/browser/resources/md_history/side_bar.html (right):

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/side_bar.html:45: <paper-listbox id="menu"
selected="[[routeData.page]]"
On 2016/06/08 03:42:17, tsergeant wrote:
> Should this be 2-way bound?

Nah.

https://codereview.chromium.org/2042973002/diff/20001/chrome/browser/resource...
chrome/browser/resources/md_history/side_bar.html:48: <paper-item
view-id="history-list" class="page-item" path="">
On 2016/06/08 03:42:18, tsergeant wrote:
> This element has a bunch of extra logic to work with the awkwardness around
> selectedPage vs route.
> 
> You might be able to simplify this logic a bunch by using <a> tags. Then the
> flow becomes:
> 
> click <a> -> app-route updates -> selected page updates -> sidebar selection
> updates.
> 
> We would also get the other benefits of <a> tags like being able to middle
> click.

Done.

https://codereview.chromium.org/2042973002/diff/20001/ui/webui/resources/poly...
File ui/webui/resources/polymer_resources.grdp (right):

https://codereview.chromium.org/2042973002/diff/20001/ui/webui/resources/poly...
ui/webui/resources/polymer_resources.grdp:23: <structure
name="IDR_POLYMER_1_0_APP_ROUTE_APP_LOCATION_EXTRACTED_JS"
On 2016/06/08 03:42:18, tsergeant wrote:
> You can remove app-route from third_party/polymer/v1_0/find_unused_elements.py

Done.

[calamity, 2016-06-15 06:27:55]

Reinstated selectedPage_ as discussed.

[calamity, 2016-06-16 00:47:57]

Patchset #8 (id:140001) has been deleted

[calamity, 2016-06-16 06:24:54]

Patchset #8 (id:160001) has been deleted

[calamity, 2016-07-13 06:30:03]

Updated! PTAL, thanks.

[tsergeant, 2016-07-13 07:23:33]

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
File chrome/browser/resources/md_history/app.js (right):

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/app.js:209: getSelectedPage_(selectedPage,
items) {
If I understand correctly, this only exists to force the selection to
re-evaluate after the synced device manager is created.

That's fairly subtle behavior, so it would be nice to document it.

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
File chrome/browser/resources/md_history/side_bar.html (right):

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:6: <link rel="import"
href="chrome://resources/polymer/v1_0/paper-listbox/paper-listbox.html">
Listbox is unused, paper-item-shared-styles might be too?

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:51: iron-selector a {
Replacing paper-item with this CSS removes the focus highlight from the menu
items.

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:89:
<paper-ripple></paper-ripple>
The ripples were intentionally deleted from the sidebar, no need for them to
come back =)

(and if you remove the <paper-ripple> maybe you can have just the <a> with no
inner <div>?)

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:96: <a
href="chrome://settings/clearBrowserData" id="clear-browsing-data">
I changed this button to use a chrome.send call, rebase to bring that change
back.

[calamity, 2016-07-14 03:40:26]

Description was changed from

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation
==========

to

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.linux:closure_compilation
==========

[calamity, 2016-07-14 06:20:57]

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
File chrome/browser/resources/md_history/app.js (right):

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/app.js:209: getSelectedPage_(selectedPage,
items) {
On 2016/07/13 07:23:33, tsergeant wrote:
> If I understand correctly, this only exists to force the selection to
> re-evaluate after the synced device manager is created.
> 
> That's fairly subtle behavior, so it would be nice to document it.

Good point. Done.

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
File chrome/browser/resources/md_history/side_bar.html (right):

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:6: <link rel="import"
href="chrome://resources/polymer/v1_0/paper-listbox/paper-listbox.html">
On 2016/07/13 07:23:33, tsergeant wrote:
> Listbox is unused, paper-item-shared-styles might be too?

paper-item-shared-styles are used for --paper-font-subhead but that include can
be made more specific.

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:51: iron-selector a {
On 2016/07/13 07:23:33, tsergeant wrote:
> Replacing paper-item with this CSS removes the focus highlight from the menu
> items.

Fixed.

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:89:
<paper-ripple></paper-ripple>
On 2016/07/13 07:23:33, tsergeant wrote:
> The ripples were intentionally deleted from the sidebar, no need for them to
> come back =)
> 
> (and if you remove the <paper-ripple> maybe you can have just the <a> with no
> inner <div>?)

Done.

https://codereview.chromium.org/2042973002/diff/260001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:96: <a
href="chrome://settings/clearBrowserData" id="clear-browsing-data">
On 2016/07/13 07:23:33, tsergeant wrote:
> I changed this button to use a chrome.send call, rebase to bring that change
> back.

Done.

[tsergeant, 2016-07-15 03:56:14]

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
File chrome/browser/resources/md_history/app.js (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
chrome/browser/resources/md_history/app.js:206: * fallback selection will
continue to be used after the corresponding item is
An impressive set of 80 character lines here.

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
File chrome/browser/resources/md_history/side_bar.html (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:107: <a
on-tap="onClearBrowsingDataTap_" id="clear-browsing-data">
An <a> without an href="" is kind of like a plain old span, which means you
can't tab to it and you can't right click or middle click it like a regular
link.

You can improve this by doing <a href="#" ...>, which lets you tab to it and use
enter or space to open CBD. But then if you middle click the link, you get
chrome://history open in a new tab.

The best solution here seems to be:
<a href="chrome://settings/clearBrowserData" on-tap="...">

Then in onClearBrowsingDataTap_, preventDefault on the tap event.

This way:
- the <a> has the correct a11y values
- clicking or pressing enter uses the chrome.send version
- middle clicking or right-click -> new tab works as expected.

https://codereview.chromium.org/2042973002/diff/360001/chrome/test/data/webui...
File chrome/test/data/webui/md_history/history_routing_test.js (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/test/data/webui...
chrome/test/data/webui/md_history/history_routing_test.js:7:
suite('synced-tabs', function() {
Nit: Rename this suite.

https://codereview.chromium.org/2042973002/diff/360001/chrome/test/data/webui...
chrome/test/data/webui/md_history/history_routing_test.js:20:
assertEquals('syncedTabs', app.$.content.selected);
Nit: Maybe assert that the URL is correct?

[Dan Beam, 2016-07-15 04:23:41]

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
File chrome/browser/resources/md_history/app.js (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
chrome/browser/resources/md_history/app.js:206: * fallback selection will
continue to be used after the corresponding item is
On 2016/07/15 03:56:14, tsergeant wrote:
> An impressive set of 80 character lines here.

+1 /golfclap

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
File chrome/browser/resources/md_history/side_bar.html (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:100: <a href="/"
class="page-item" path="history">
why is it worthwhile to switch to <a href> here?  do you really want
right/middle click options this badly?  settings did not feel the need to do
this, as I don't really think there's a big use case for right click > copy URL
or opening in new tabs.

[calamity, 2016-07-15 06:22:02]

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
File chrome/browser/resources/md_history/app.js (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
chrome/browser/resources/md_history/app.js:206: * fallback selection will
continue to be used after the corresponding item is
On 2016/07/15 04:23:40, Dan Beam wrote:
> On 2016/07/15 03:56:14, tsergeant wrote:
> > An impressive set of 80 character lines here.
> 
> +1 /golfclap

Acknowledged.

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
File chrome/browser/resources/md_history/side_bar.html (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:100: <a href="/"
class="page-item" path="history">
On 2016/07/15 04:23:40, Dan Beam wrote:
> why is it worthwhile to switch to <a href> here?  do you really want
> right/middle click options this badly?  settings did not feel the need to do
> this, as I don't really think there's a big use case for right click > copy
URL
> or opening in new tabs.

I'm not 100% sure if this is true, but it seems that app-route is 'nicer' if you
use <a href>s to change your state. It's the way SHOP does it as well.

I did have a data-bound version earlier, but it was getting complicated to
decide who has responsibility for what. <a href>s mean that the data flow is
always top down (click, app-location notifies down the route hierarchy and
everyone changes as necessary).

This is a bit messy with all the CSS, but once paper-item-shared-styles is fixed
to be more... shareable, the nastiness above will hopefully go away.

https://codereview.chromium.org/2042973002/diff/360001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.html:107: <a
on-tap="onClearBrowsingDataTap_" id="clear-browsing-data">
On 2016/07/15 03:56:14, tsergeant wrote:
> An <a> without an href="" is kind of like a plain old span, which means you
> can't tab to it and you can't right click or middle click it like a regular
> link.
> 
> You can improve this by doing <a href="#" ...>, which lets you tab to it and
use
> enter or space to open CBD. But then if you middle click the link, you get
> chrome://history open in a new tab.
> 
> The best solution here seems to be:
> <a href="chrome://settings/clearBrowserData" on-tap="...">
> 
> Then in onClearBrowsingDataTap_, preventDefault on the tap event.
> 
> This way:
> - the <a> has the correct a11y values
> - clicking or pressing enter uses the chrome.send version
> - middle clicking or right-click -> new tab works as expected.

Ace Investigation. Done.

https://codereview.chromium.org/2042973002/diff/360001/chrome/test/data/webui...
File chrome/test/data/webui/md_history/history_routing_test.js (right):

https://codereview.chromium.org/2042973002/diff/360001/chrome/test/data/webui...
chrome/test/data/webui/md_history/history_routing_test.js:7:
suite('synced-tabs', function() {
On 2016/07/15 03:56:14, tsergeant wrote:
> Nit: Rename this suite.

Done.

https://codereview.chromium.org/2042973002/diff/360001/chrome/test/data/webui...
chrome/test/data/webui/md_history/history_routing_test.js:20:
assertEquals('syncedTabs', app.$.content.selected);
On 2016/07/15 03:56:14, tsergeant wrote:
> Nit: Maybe assert that the URL is correct?

Done.

[tsergeant, 2016-07-18 01:33:26]

lgtm with 1 nit

https://codereview.chromium.org/2042973002/diff/380001/chrome/browser/resourc...
File chrome/browser/resources/md_history/side_bar.js (right):

https://codereview.chromium.org/2042973002/diff/380001/chrome/browser/resourc...
chrome/browser/resources/md_history/side_bar.js:35: * Relocates the user to the
clear browsing data section of the settings page.
Nit: @param for e

[calamity, 2016-07-18 04:54:53]

calamity@chromium.org changed reviewers:
+ michaelpg@chromium.org

[calamity, 2016-07-18 04:54:54]

+michaelpg for find_unused_elements.py and polymer_resources.grdp

[michaelpg, 2016-07-18 19:06:38]

https://codereview.chromium.org/2042973002/diff/400001/ui/webui/resources/pol...
File ui/webui/resources/polymer_resources.grdp (right):

https://codereview.chromium.org/2042973002/diff/400001/ui/webui/resources/pol...
ui/webui/resources/polymer_resources.grdp:47: <structure
name="IDR_POLYMER_1_0_APP_ROUTE_APP_ROUTE_CONVERTER_EXTRACTED_JS"
this & below seem to be unused

[calamity, 2016-07-19 01:41:37]

https://codereview.chromium.org/2042973002/diff/400001/ui/webui/resources/pol...
File ui/webui/resources/polymer_resources.grdp (right):

https://codereview.chromium.org/2042973002/diff/400001/ui/webui/resources/pol...
ui/webui/resources/polymer_resources.grdp:47: <structure
name="IDR_POLYMER_1_0_APP_ROUTE_APP_ROUTE_CONVERTER_EXTRACTED_JS"
On 2016/07/18 19:06:38, michaelpg wrote:
> this & below seem to be unused

These are dependencies of app-route/app-location.

[calamity, 2016-07-19 01:45:31]

On 2016/07/19 01:41:37, calamity wrote:
>
https://codereview.chromium.org/2042973002/diff/400001/ui/webui/resources/pol...
> File ui/webui/resources/polymer_resources.grdp (right):
> 
>
https://codereview.chromium.org/2042973002/diff/400001/ui/webui/resources/pol...
> ui/webui/resources/polymer_resources.grdp:47: <structure
> name="IDR_POLYMER_1_0_APP_ROUTE_APP_ROUTE_CONVERTER_EXTRACTED_JS"
> On 2016/07/18 19:06:38, michaelpg wrote:
> > this & below seem to be unused
> 
> These are dependencies of app-route/app-location.

Oops, never mind. You're right.

[michaelpg, 2016-07-19 20:34:03]

lgtm

[tsergeant, 2016-07-20 01:53:33]

The CQ bit was checked by tsergeant@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-20 01:54:12]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-20 01:54:15]

Your CL relies on deprecated CQ feature(s):
 * Specifying master names in CQ_INCLUDE_TRYBOTS part of description without
"master." prefix is deprecated:
     tryserver.chromium.linux
   For more details, see http://crbug.com/617627.

[commit-bot: I haz the power, 2016-07-20 03:15:43]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-20 03:15:44]

Dry run: This issue passed the CQ dry run.

[calamity, 2016-07-20 03:22:04]

The CQ bit was checked by calamity@chromium.org

[calamity, 2016-07-20 03:22:05]

The patchset sent to the CQ was uploaded after l-g-t-m from
tsergeant@chromium.org
Link to the patchset: https://codereview.chromium.org/2042973002/#ps440001
(title: "rebase")

[commit-bot: I haz the power, 2016-07-20 03:22:42]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-20 03:22:44]

Your CL relies on deprecated CQ feature(s):
 * Specifying master names in CQ_INCLUDE_TRYBOTS part of description without
"master." prefix is deprecated:
     tryserver.chromium.linux
   For more details, see http://crbug.com/617627.

[commit-bot: I haz the power, 2016-07-20 04:32:51]

Committed patchset #21 (id:440001)

[commit-bot: I haz the power, 2016-07-20 04:32:56]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-20 04:35:10]

Description was changed from

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.linux:closure_compilation
==========

to

==========
[MD History] Add routing to the history page.

This CL adds app-route to the Material Design History page so that
chrome://history/openTabs goes to the synced devices view and clicking
the synced devices button in the sidebar also modifies the location bar.

BUG=609502
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.linux:closure_compilation

Committed: https://crrev.com/357edd888ea83097acfec6125c6cb478d2499d03
Cr-Commit-Position: refs/heads/master@{#406488}
==========

[commit-bot: I haz the power, 2016-07-20 04:35:12]

Patchset 21 (id:??) landed as
https://crrev.com/357edd888ea83097acfec6125c6cb478d2499d03
Cr-Commit-Position: refs/heads/master@{#406488}