Autocomplete from bookmarks doesn't work when I delete all history, until I delete places.sqlite, but then stops working again next time the history is cleared.
I've noticed that with the latest update (62.0, I think), autocomplete won't work for bookmarks when the browsing and download history is deleted. I discovered this by looking into why autocomplete wouldn't work and finding this https://support.mozilla.org/en-US/questions/1180019, so I deleted the places.sqlite file and that fixed it. That is, until the next time I deleted the browsing and download history. So I guess for now I could try to automate the process of deleting places.sqlite every time I clear the history, but I would like to find some internal Firefox setting or something that would fix this permanently.
วิธีแก้ปัญหาที่เลือก
Hi pafirefox
I think this is bug that will hopefully be fixed soon:
Bug 1488879 Address bar does not autofill unvisited bookmark URLs
Cheers!
..Roland
อ่านคำตอบนี้ในบริบท 👍 0การตอบกลับทั้งหมด (5)
please try a Refresh but Note that this does more than uninstalling and re-installing does. Normal uninstalling does not remove some preferences which may have become corrupt. Please Refresh but do this 1st:
- https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer
- https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles
then
TEST....... If no issues then Extensions which need to be added back in 1 at a time and tested ..... Or it is your Profile : Make a new one and test ...:
If is your Profile :
How are you clearing that history?
Is that via internal means or are you using an external application?
cor-el said
How are you clearing that history? Is that via internal means or are you using an external application?
It's being cleared via internal means.
วิธีแก้ปัญหาที่เลือก
Hi pafirefox
I think this is bug that will hopefully be fixed soon:
Bug 1488879 Address bar does not autofill unvisited bookmark URLs
Cheers!
..Roland
Pkshadow, I tried the refresh, but even without restoring my profile or installing a single extension, the bug persisted. Roland Tanglao, thanks!