Closed Bug 46584 Opened 26 years ago Closed 25 years ago

[RFE]Mistyped url's shouldn't be added to url dropdown history widget.

Categories

(SeaMonkey :: Location Bar, enhancement, P3)

enhancement

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 9203
Future

People

(Reporter: gregm, Assigned: alecf)

Details

Type www.cnn.co (or some other name that can't be resolved) this happily gets added to the history. Maybe it should be removed if it can't be resolved and save the history for urls/hostnames that actually work? Just a thought
I don't seen unresolved URLs in my history list, or in the back and/or forward drop down lists. I'm on Red Hat 6.2, build id 2000072621 and user-agent: Mozilla/5.0 (X11; U; Linux 2.2.14-5.0 i686; en-US; m17) Gecko/20000726 Reporter, do you still see this on newer builds? If so reopen the bug and give more details on what platform and where you see the URL in the history list.
Status: UNCONFIRMED → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
On 2000072521 (pulling down latest now) Do the following: 1. type http://www.mozilla.dir/ in the url bar and hit return. 2. The Following is output in the console that is running moz. Entry at index 0 is http://www.mozilla.dir Document: Done (11.595 secs) 3. Click on the arrow next to the search button (modern skin) Note that the entry at index (x) is the http://www.mozilla.dir It however don't show up in the back/forward history.
Build 2000072621 exhibits the same behavior.
aha! reopening and tweaking summary
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Summary: Mistyped url's shouldn't be added to history. → Mistyped url's shouldn't be added to url dropdown history widget.
I can confirm this with 2000073108 builds. However this is the way 4.x worked and i wonder if changing this behavior would be a) difficult and/or b) cause other usability headaches
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Yes 4.xx does this, this way, and its irritating Maybe a RFE?
Summary: Mistyped url's shouldn't be added to url dropdown history widget. → [RFE]Mistyped url's shouldn't be added to url dropdown history widget.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
I disagree with this proposal. If I want to correct the misspelled URL later, I have to retype all of it. The urlbar history should work just like any other history of a textfield - keep the history of *text* I typed, not the history of URLs I visited using the urlbar. I suggest WONTFIX.
The problem is you pull the incorrectly typed url up, correct it, now you have the incorrect and correct url in the history.
where is the problem? W2K's textfield history boxes behave the same, not?
nav triage team: looked at this bug, it is not a beta stopper. bulk update of several such bugs.
Keywords: nsbeta1-
*** Bug 66049 has been marked as a duplicate of this bug. ***
Sorry about the dupe, but this is just annoying. I would agree with the urlbar being a history of what you typed instead of where you went if it didn't try to autocomplete to the misstyped url. You have no idea how many times I've seen the nslookup error box. I don't think making the urlbar consistent with w2k's text boxes is a good idea, because in this case it doesn't make sense to and leads to more headaches then it's worth.
No DUP. Autocomplete != history (at least theoretically, dunno about the code). I agree that bug 66049 should be fixed (unlike this one). I'll reopen the other bug.
moving these bugs to History: URLBar
Assignee: radha → alecf
Status: ASSIGNED → NEW
Component: History: Session → History: URLBar
I think this is a dup of bug 9203.
*** This bug has been marked as a duplicate of 9203 ***
Status: NEW → RESOLVED
Closed: 26 years ago25 years ago
Resolution: --- → DUPLICATE
dupe of Bug 9203 [RFE] making it so that it does not save 'dead' or incorect url's in the location drop down
Status: RESOLVED → VERIFIED
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.