Domain for a URL that was visited in the past doesn’t move to today when visited again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
webbrowser-app |
Fix Released
|
High
|
Olivier Tilloy | ||
webbrowser-app (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
To reproduce reliably this issue, you may need to craft a navigation history database for the browser manually.
The database can be edited with sqlite3 at "~/.local/
To insert an entry, do something like that:
insert into history (url, title, visits, lastVisit) values("http://
To generate a timestamp in the past, you can use a command similar to this one:
python -c "import datetime, time; print int(time.
To reproduce the issue, start with a clean history database (just remove the history.sqlite file and let the app re-create it).
Close the application, edit the history and add an entry for a given URL (e.g. "http://
Expected result: the domain entry (ubuntu.com) moves from the "last month" section to "Today".
Current result: the domain entry remains in "last month".
Related branches
- PS Jenkins bot: Approve (continuous-integration)
- Günter Schwann (community): Approve
-
Diff: 115 lines (+8/-21)5 files modifiedsrc/Ubuntu/Components/Extras/Browser/history-domain-model.cpp (+1/-1)
src/Ubuntu/Components/Extras/Browser/history-domainlist-model.cpp (+3/-5)
src/Ubuntu/Components/Extras/Browser/history-timeframe-model.cpp (+2/-2)
tests/unittests/history-domainlist-model/tst_HistoryDomainListModelTests.cpp (+0/-13)
tests/unittests/history-timeframe-model/tst_HistoryTimeframeModelTests.cpp (+2/-0)
Changed in webbrowser-app: | |
status: | New → Confirmed |
Changed in webbrowser-app: | |
importance: | Undecided → High |
assignee: | nobody → Olivier Tilloy (osomon) |
summary: |
- Domain that was visited in the past doesn’t move to today when visited - again + Domain for a URL that was visited in the past doesn’t move to today when + visited again |
Changed in webbrowser-app: | |
status: | Fix Committed → Fix Released |
It looks like the root cause is the same as bug #1207233.