Closed
Bug 834541
Opened 12 years ago
Closed 7 years ago
remove hasHistoryEntries
Categories
(Toolkit :: Places, defect, P3)
Toolkit
Places
Tracking
()
RESOLVED
FIXED
mozilla62
Tracking | Status | |
---|---|---|
firefox62 | --- | fixed |
People
(Reporter: mak, Assigned: mak)
References
Details
(Whiteboard: [fxsearch])
Attachments
(1 file)
hasHistoryEntries is cached most of the time, though sometimes we have to requery, and that query is synchronous.
Updated•11 years ago
|
Blocks: fxdesktopbacklog
Whiteboard: p=0
Updated•10 years ago
|
Assignee | ||
Comment 1•10 years ago
|
||
a couple instances in WindowsJumpLists.jsm could be easily converted to be async.
The one on shutdown could be converted using AsyncShutdown...
but actually, if we could completely remove the API, it would be even better.
WindowsJumpLists.jsm is the only _external_ consumer in our code, the instances in queries are there just as micro optimizations (don't even query if we know there's no history), we could just ignore those optimizations since they only help someone that doesn't have any history (very small minority of users).
The check on shutdown is basically a "did we run clear history on shutdown?" question, and we can figure a better way to reply that question that doesn't involve disk access or even knowing if there's history (it could listen to a clear on shutdown topic or directly to history, unfortunately "shutdown-cleanse" has gone).
Assignee | ||
Updated•10 years ago
|
Points: --- → 5
Flags: qe-verify-
Whiteboard: p=13 [qa?]
Assignee | ||
Updated•10 years ago
|
Summary: make hasHistoryEntries asynchronous → make hasHistoryEntries asynchronous and deprecate it
Assignee | ||
Updated•10 years ago
|
Summary: make hasHistoryEntries asynchronous and deprecate it → remove hasHistoryEntries
Assignee | ||
Updated•9 years ago
|
Priority: -- → P2
Assignee | ||
Updated•7 years ago
|
Priority: P2 → P3
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → mak77
Status: NEW → ASSIGNED
Whiteboard: [fxsearch]
Comment hidden (mozreview-request) |
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8973949 [details]
Bug 834541 - Remove the public History.hasHistoryEntries synchronous API.
https://reviewboard.mozilla.org/r/242280/#review248504
Attachment #8973949 -
Flags: review?(standard8) → review+
Comment 5•7 years ago
|
||
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.
hg error in cmd: hg rebase -s 8f16311fb00e415258833ff313a9982bf5e32c4b -d 2d5c99b70e34: rebasing 462825:8f16311fb00e "Bug 834541 - Remove the public History.hasHistoryEntries synchronous API. r=standard8" (tip)
merging toolkit/components/places/nsNavHistory.cpp
merging toolkit/components/places/nsNavHistory.h
merging toolkit/components/places/nsNavHistoryResult.cpp
merging toolkit/components/places/tests/unit/test_browserhistory.js
warning: conflicts while merging toolkit/components/places/nsNavHistory.h! (edit, then use 'hg resolve --mark')
warning: conflicts while merging toolkit/components/places/tests/unit/test_browserhistory.js! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 10•7 years ago
|
||
Pushed by mak77@bonardo.net:
https://hg.mozilla.org/integration/autoland/rev/80cabc246b5f
Remove the public History.hasHistoryEntries synchronous API. r=standard8
Comment 11•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•