Closed Bug 590925 Opened 15 years ago Closed 14 years ago

autocomplete not working since MAC OS update, 08/26/2010

Categories

(Camino Graveyard :: Location Bar & Autocomplete, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ian.orourke, Unassigned)

Details

(Whiteboard: [CLOSEME 1/15])

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.0.19) Gecko/2010051911 Camino/2.0.3 (like Firefox/3.0.19) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.0.19) Gecko/2010051911 Camino/2.0.3 (like Firefox/3.0.19) The address bar is not showing completed urls when you begin typing. E.g.If gmail.com is in your history. Then when you start typing gm.....it should be displayed below as a link to click. Reproducible: Always
If you show history, is "gmail.com" present? If you try a fresh profile (http://pimpmycamino.com/parts/troubleshoot-camino can automate this for you for testing purposes), visit gmail.com, show history to verify that "gmail.com" is present in history, and then type "gmail.com" in the location bar, does autocomplete work?
Ye, the history is present. The MAC couldn't reboot yesterday as Camino wont close, had to Force Quit it. Some strange behavior when typing urls, each letter typed was hilighted and every subsequent letter typed just replaced the previous. I'm running synergy share mouse and keyboard, would that be the issue.
Did you try a fresh profile as described in the second paragraph of comment 1? Was the problem still present? (In reply to comment #2) > I'm running synergy share mouse and keyboard, would that be the issue. Possibly; can you disable Synergy, restart, and see if the problem goes away?
Summary: cached webpages not autocompleting since MAC OS update, 08/26/2010 → autocomplete not working since MAC OS update, 08/26/2010
Can you please answer the questions in comment 3?
Whiteboard: [CLOSEME 1/15]
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.