Closed
Bug 110203
Opened 23 years ago
Closed 23 years ago
URL autocomplete broken [trunk only]
Categories
(SeaMonkey :: Location Bar, defect)
SeaMonkey
Location Bar
Tracking
(Not tracked)
VERIFIED
WORKSFORME
mozilla0.9.7
People
(Reporter: piskozub, Assigned: hewitt)
References
Details
(Keywords: regression)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.5+) Gecko/20011114
BuildID: 20011114
Today between 0930 and 1830 (Pacific time), URL autocomplete feature has been
completely broken. The new build does not autocomplete, nor does it show the
dropdown menu.
Tested with WindowsME builds made from two CVS trees, one pulled at
(20011114)0930 the other 1830. Autocomplete in the former works and in the
latter doesn't.
Reproducible: Always
Steps to Reproduce:
1. Try to type any valid URL
2. Do it a second time
3. Do it any number of times with no autocomplete action visible
Reporter | ||
Comment 2•23 years ago
|
||
After the checkin for bug 108543, the Search dropdown started to appear again
(as it should) but this is still the only visible autocomplete activity.
Assignee | ||
Comment 3•23 years ago
|
||
Oh, how delightful! I will just have to update my tree tomorrow morning to
experience this for myself.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.7
Comment 4•23 years ago
|
||
Same under MacOS 8.6 2001111504
Platform should be All.
Reporter | ||
Comment 6•23 years ago
|
||
WFM with a fresh CVS build (around 2001111509). However it did notwork just
after compiling the build. The thing I had to do was deleting component.reg and
XUL.mfl *and* rebooting Windows. I did it trying to get rid of bug 110202. After
the reboot both bugs WFM. Probably deleting both files was an overkill. I am not
sure which was the importent one, though.
Reporter | ||
Comment 7•23 years ago
|
||
I retract my last comment. I tested with the wrong CVS tree (I have three now).
The solution described worked for bug 110202 but not for this one. Sorry.
Comment 8•23 years ago
|
||
yet another regression on autocomplete
i will notify the "0.9.6 dont suck" team
Keywords: regression
Comment 9•23 years ago
|
||
Someone can confirm this on the latest branch? If this affects branch, this is
blocker. If not, please change summary to reflect trunk-only
Comment 10•23 years ago
|
||
trunk only, so not blocking 0.9.6
Summary: URL autocomplete broken → URL autocomplete broken [trunk only]
Comment 11•23 years ago
|
||
BTW, this works again in the 15:42 2001111503 build. (at least for me - WinMe)
Comment 12•23 years ago
|
||
WFM too, 2001111503, WinME
Comment 13•23 years ago
|
||
I've triple-checked this, but Autocomplete does work in the non-talkback Win32
zip, but *not* with the talkback zip. (built at 3:44:00 PM and 3:43:00 PM,
respectively) I'm on Win98SE
Comment 14•23 years ago
|
||
*** Bug 110467 has been marked as a duplicate of this bug. ***
Comment 15•23 years ago
|
||
I think this is releated to this history foobar that we had yesterday ?
Obviously if history isnt working then Autocomplete won't work either.
WFM 2001111503 Win2k
Reporter | ||
Comment 16•23 years ago
|
||
WFM with 2001111605 installer build on WindowsME. Cannot test with fresh CVS
builds as they crash on launch.
Comment 17•23 years ago
|
||
WFM on trunk 2001111521 and fresh CVS build, Linux.
Comment 18•23 years ago
|
||
Ok, marking WFM. Someone else verify
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Comment 19•23 years ago
|
||
Francisco: Is your WFM based on the "regular" or "talkback" build?
(See also comment #13)
Comment 20•23 years ago
|
||
Verified WFM on 2001111603 Talkback builds (Trunk) Windows 2000 SP 2
Status: RESOLVED → VERIFIED
Comment 21•23 years ago
|
||
Autocomplete is broken in Trunk 2001111908 under MacOS 8.6. This bug should be
reopen.
Comment 22•23 years ago
|
||
WFM in 2001112004...
Comment 23•23 years ago
|
||
scott tran, don't go around verifying (as in marking VERIFIED) random bugs
unless you are fully qualified to do so. You'll know you are qualified when
someone tells you "you can mark (my) bugs verified" OR you are the QA
Contact(possibly reporter) on a bug.
In this case this bug was seen on ALL platforms and needs to be verified on all
platforms.
It is very helpful, and entirely sufficient to simply add your verificaton as a
comment like comments #16 and #17
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•