Why Aren't All Page Visits Shown in SHOW FULL HISTORY

Note: I asked this question in January. That thread is closed, so I am starting over here.

Question: why does Show Full History exclude some page visits?

STEPS TO REPRODUCE PROBLEM
STEP 1 - Vist the following urls in the order listed:

https://www.google.com/
https://www.straighttalk.com/
https://rumble.com/c/BannonsWarRoom
https://www.devtopics.com/best-programming-jokes/

STEP 2 - OPEN MENU->HISTORY->SHOW FULL HISTORY

STEP 3 - VERIFY THE FOUR MOST RECENT ENTRIES MATCH THE FOR PAGE VISITS IN STEP 1 ABOVE

STEP 4 - NAVIGATE TO THE FOLLOWING URL
https://rumble.com/c/BannonsWarRoom

STEP 5 - SHOW FULL HISTORY. IT WILL LOOK LIKE THIS

PROBLEM: What happened to the visit to Bannon’s War Room after Straight Talk and before Best Programming Jokes?

Answer suggested in original thread:

MattchesBrowser Support

Jan 13

@carla_rogers,
I believe that this is because the page is static and still stored in the browsers cache. When you visit the site again, it is fetched again and moved to the top of the list. This is the expected behavior — you can see the same behavior in Chrome and other chromium based browsers as well.

RESPONSE TO ANSWER PROPOSED IN ORIGINAL THREAD:
Same result occurs when cache is disabled (via developer tools->network>checkbox for disable browser cache).

The history database used by Brave records every page visit. To see this, use sqllite and open the history file in your profile directory (on MacOS: /Users//Library/Application Support/BraveSoftware/Brave-Browser-Nightly/Default/History)

List the five most recent page visits:

Now you can see both visits to Bannon’s War Room, not only the most recent one.

The sql for that is:

select 
v.id,
u.url, 
u.title,
v.visit_time,
datetime(v.visit_time / 1000000 + (strftime('%s', '1601-01-01')), 'unixepoch', 'localtime') as visit_time
from visits v
left join urls u on v.url = u.id
order by v.visit_time desc
limit 5;

So, why doesn’t Show Full History show the full history?

P.S. All browsers behave this way. I think it sucks in every case

@carla_rogers,
I will ask for further clarification on this — however, as you (and I) stated, this does seem to be the default behavior for most browsers. As such, the best I can provide you will likely be a technical explanation, rather than a fix of any kind.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.