I've run into a few issues repeatedly when trying to "find a website when I know roughly when I saw it once before". Meaning I expect 'history' to... "Show every URL I've gone to before, starting with now and going backward in time. Without any further input by me to get that order, and keep showing more if I keep scrolling down. With 'search' happening across all time unless I tell it otherwise." Issue 1: I've run into some filtering (missing entries I know should exist) unless I "press alt while opening history"? I haven't searched to figure out how/why that helps, but thank you random Reddit person for the suggestion/workaround. Guess I should do that next, but I swear I tried to search already and couldn't find a description (nor explanation for shortcuts related to history beyond the obvious). Issue 2: Yes, filtering down to day by day probably makes certain operations more efficient (the current forced buckets on the left). But it makes the user need to do more work, which feels like a 'bad thing'. Meaning instead of click text field then search... I tend to click text field, then remember I need to pick the correct 'day(s)' bucket (unless I'm searching only today, which is rare for me), then click search again, and finally type what to search by. Issue 3: Today I just noticed that there is no column to sort by that'll display in 'when visited' order, only 'last visited'. Meaning they won't necessarily appear in the order that I visited them (what I assumed a history's default sort order should be). Sure, it's easier/simpler and uses less space to only record the most recent visit. But that breaks any true/simple (chronological) visit history, right? If I search for a place I visit often I'd expect to be able to see all visits as rows. Anyway, I don't know all the reasons for changing to what I see now, but I hesitate to file a bug (or 3) yet. Is this what a modern history should be? Am I just a dinosaur with how I expect it to function still? And it'd be all better if I could just [insert new paradigm or feature] instead.
... View more