To clarify - history from two different devices of the same model (e.g. two Nexus 5 phones) is shown as coming from one device?

Sky, did you try to repro this bug?

Re: #6, I was taking ownership to track closing out the bug due to inactivity.

However, tried to test this really quickly last week, and I ran into some odd behavior where multiple clients connected from the save device didn't appear to create sessions data. I don't understand what exactly is going on, it seems they make the commit request, get seemingly real server ids, but their versions don't increment. I cannot find the actual data stored when looking up by server id. I will try to spend more time investigating this week.

Looks like my previous comments were just running into  issue 688045  and getting confused from that.

Assigning to msramek@, looking at the MD chrome://history page (not Tabs from other devices), I don't see any indication of the device the history row came from. Additionally, typing the host name into the search box at the top, doesn't seem to be matching against the host name it originated from. I think this is the problem the reporter was having. They were likely looking for a history record from a particular device, they could remember which device they were using, and they wanted to narrow down their search by that criteria.

I'm not sure what kind of considerations have gone into the new MD history page, perhaps you can shed some light on if this is WAI for if this is functionality we want to add in the future.

> I don't see any indication of the device the history row came from

I don't think this was ever supported. Even though Sync must be able to distinguish individual devices, AFAIK history.google.com (where we fetch the results from) does not.

Furthermore, there is also a UX question. We lump visits to the same URL from the same day into one history page entry. So the same news article visited on my desktop and on my phone is one entry. Does it make sense to break it into two?

> Additionally, typing the host name into the search box at the top, doesn't seem to be matching against the host name it originated from.

That search box searches history entries, not device names, I think. This is probably worth improving. Then there is also the problem that the search box can sometimes behave weirdly for short queries, that's issue 686884. This is "working as implemented", I'm afraid, and probably also worth revisiting.

> I'm not sure what kind of considerations have gone into the new MD history page

Me neither :) Reassigning to +calamity@, tsergeant@ if you want to have a look at some of these issues.