Closed
Bug 78243
Opened 24 years ago
Closed 24 years ago
open history db when autocomplete starts
Categories
(SeaMonkey :: Location Bar, defect, P2)
SeaMonkey
Location Bar
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.1
People
(Reporter: hewitt, Assigned: alecf)
References
Details
(Whiteboard: fix in hand)
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
Currently, the history DB isn't loaded until you visit a webpage. This kills
the autocomplete widget for people who have no homepage, and try to type a url
before loading a page.
I realize this was probably a startup perf enhancement, but I think it needs to
go, or else autocomplete won't work.
Comment 2•24 years ago
|
||
Sounds like the API could use a little love. If you fail to look up the URL bar
contents in the history, can't you just send it down the stack to networking anyway?
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Summary: stop loading history db lazily → open history db when autocomplete starts
Target Milestone: --- → mozilla0.9.1
Assignee | ||
Comment 4•24 years ago
|
||
the problem is not that it is loaded lazily. the problem is we need to load it
when autocomplete starts. This should be as simple as putting OpenDB() in the
beginning of whatever the first call Autocomplete calls..I should have caught
this in my review :)
Assignee | ||
Comment 6•24 years ago
|
||
Reporter | ||
Comment 7•24 years ago
|
||
r=hewitt
Assignee | ||
Comment 9•24 years ago
|
||
fix is in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 10•24 years ago
|
||
*** Bug 78438 has been marked as a duplicate of this bug. ***
Comment 11•24 years ago
|
||
*** Bug 78499 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 12•24 years ago
|
||
*** Bug 78492 has been marked as a duplicate of this bug. ***
Comment 13•23 years ago
|
||
VERIFIED Fixed in 2001060704 builds (modulo the 1st instance bug)
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•