Where exactly are you clicking? 

In 55.2853 on Windows, I can navigate to the history entry's page by clicking on the "Title" portion of the history item; clicking on the hostname portion has no effect. 

Deleted: ok.png 14.4 KB

	ok.png 14.4 KB View Download

my version 55.0.2853.0 seems to be running the material design redesign which doesn't have hyperlinks.

Deleted: cant click.png 16.3 KB

	cant click.png 16.3 KB View Download

I suspect this has to do with polymer and iron-selector

The link is clearly found in the href, however it is simply not clickable

<div id="title-and-domain">
            <a id="title" class="website-title" href="https://www.google.com/webhp?sourceid=chrome-instant&amp;ion=1&amp;espv=2&amp;ie=UTF-8#q=how%20to%20take%20a%20screenshot" title="https://www.google.com/webhp?sourceid=chrome-instant&amp;ion=1&amp;espv=2&amp;ie=UTF-8#q=how%20to%20take%20a%20screenshot">
              <history-searched-label>https://www.google.com/webhp?sourceid=chrome-instant&amp;ion=1&amp;espv=2&amp;ie=UTF-8#q=how%20to%20take%20a%20screenshot</history-searched-label>
            </a>
            <span id="domain">www.google.com</span>
          </div>

I can also confirm that all history is now broken and NOTHING is clickable for the local history, however if you do happen to have other devices history available for some reason switching to those then the damned list is clickable links.  DEV build or not, being like top-level basic functionality, don't these builds actually go through any sort of testing prior to release?  And isn't the DEV channel one step past the Canary and other Alpha channels?  How did such basic top-level browser history functionality being 100% broken not get caught until the DEV build?  I've never seen a build of Firefox, IE, or any other browser for that matter ever released even in beta with basic history functionality broken.

Hi all! Thanks for the feedback.

This was an issue that was introduced in R416807 and fixed in R416868 (6 hours apart). We got unlucky with the branch for 55.0.2853.0 (R416812), and I wasn't aware until now that build made it to dev channel.

#6 -- If this is impacting your ability to use Chrome, you can disable MD History from chrome://flags/#enable-md-history.

 Issue 646956  has been merged into this issue.

tsergeant, thanks for that workaround had no idea that flag was even there!