Closed
Bug 100063
Opened 23 years ago
Closed 23 years ago
URL bar does not add http:// to start of url
Categories
(SeaMonkey :: Location Bar, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: IDontUseMozillaAnyMore, Assigned: hewitt)
Details
When you type a url without specifying a protocol Mozilla no longer assumes http:// Seen for the first time in 0.9.4
Comment 1•23 years ago
|
||
Works for me on W2K build 2001091703
Works for me using Mac/20010901311 (0.9.4). Reporter, please tell us *exactly* what you're typing into the URL bar.
Reporter | ||
Comment 3•23 years ago
|
||
I've visited http://www.ditl.org in the recent past, in fact it's my website. If I type "www.ditl.org" and press return then I don't get anything showing. This seems to be something odd about the way the return key is working or not working. Trying it some more it seems that if I type the address and press return, nothing happens. If I type the whole address and then press down arrow nothing shows in the list, but I can then press return and Mozilla will add the http:// and display correctly.
Reporter | ||
Comment 5•23 years ago
|
||
Just checked and it works fine with a new profile in build 0.9.4 (2001091311). However, the old profile doesn't work. If I go back to 0.9.3 the old profile works correctly. Maybe it's a problem that appears when certain settings are not pressent in a profile.
Reporter, in the old profile try clearing the caches and all histories.
Reporter | ||
Comment 8•23 years ago
|
||
Greg, sorry no I've just tried it and it doesn't work. I've even attempted switching off the settings for autocomplete etc and it makes no difference. If I use a new profile it all works correctly. I'm now using build 2001092804.
Reporter | ||
Comment 10•23 years ago
|
||
With a fresh profile this is now working fine. With my old 0.9.3 profile it doesn't work at all. I'll just kill the old profile and start a fresh one if you want to kill this bug?
Comment 11•23 years ago
|
||
Blake, should his 0.9.3 profile be working okay? Is there anything he can check in his profile for corruption? Should we just close this?
Comment 12•23 years ago
|
||
Ian Kennedy: could you try clearing history? I think there were some changes that caused this problem.
Comment 14•23 years ago
|
||
Ian, please respond to Additional Comment #12 on this bug.
Comment 15•23 years ago
|
||
sounds like old profile corruption
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 16•23 years ago
|
||
Appologies for the delay in getting back to this, things have been hectic at work. I've been looking at this problem for a while now and I seem to have a clearer picture of what's going on. The situation is this: 1) The trobber in the mail window will often continue to throb after the requested action is complete. (see bug 102520) 2) When you open a new browser window the focus does not pass to the URL bar. If you then click in the URL bar and start typing the auto-completion does not function correctly. Also, when you press return nothing happens. The only way to correct this is to press down-arrow, this forces the search box to drop down and then the return key will work. When the search/autocomplete box drops down it contains no information and the search line contrains 'search <x> for 'NUL'. where <x> is the choosen search engine. 3) A new issue the LDAP autocomplete feature is not working on occasion also. When this is happening it is very similar to (2) above. The composer window will open but the focus will not be in the address box. When you type in the address box it will not autocomplete, either from the local address book or the LDAP server. When you press return on the address it does not move to the next line or the subject field. From what I can see these three items seem to be related. If the throbber is still throbing and you choose to open browser window or the message compose window then the autolookup functions do not work. If the trobber is not throbbing the whole system works as it should. It looks like the throbber in an indication that some background process/service is still operating, one which both the URL bar autocomplete and the LDAP/Address book search will rely upon. I'm not familier with the code so I can't say if such a service does exist but that is my current reading of the situation. I must say that all of this is happending in versions up to 0.9.6 (2001112011) and probably beyond. The profile is freshly created today (14/12/2001) and thus it cannot be due to profile curruption, unless 0.9.6 is creating broken profiles... I've just downloaded the latest nightly and am about to try it now. HTH Ian
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reporter | ||
Comment 17•23 years ago
|
||
I've now reproduced this on 0.9.6+ build 2001120604 (which appears to be the latest nightly available for MacOS 9.x)
Comment 18•23 years ago
|
||
Ian, did you try _basic's suggestion from Comment #12?
Reporter | ||
Comment 19•23 years ago
|
||
Sorry... for got to say. Yes, I tried this. Also, this is a brand new profile freshly created and as such would have no history to clear. Thanks Ian
Comment 20•23 years ago
|
||
hoohooo *wink* try with a newer build ?
Reporter | ||
Comment 21•23 years ago
|
||
Wow! this seems to have fixed it's self. Or at least bug 102520 appears to have fixed it's self and that has fixed this bug. Nobody has attached a patch to this bug or bug 102520 so I can't see anyone working on this issue. Michael Gabriel are you aware of work that may have fixed this, or where you just asking for an update generally? It appears to be fixed in 2002021708 and maybe one or two nightly builds prior to that. It certainly wasn't fixed in the 0.9.8 initial release.
Comment 22•23 years ago
|
||
Please reopen if you can reproduce this, marking worksforme for now
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•