87250 - javascript exception 0x804b0012 in sessionHistoryUI.js when typing new address into location bar

Status: VERIFIED DUPLICATE of bug 83489

(SeaMonkey :: Location Bar, defect)

Description

[Eric Hedström]

steps:
Type a URL in the location bar and hit Enter or click the Go button. Looks like
this happens when typing in an address that is not in the history, cuz selecting
a URL from the history with either keyboard or mouse works ok.

result is this error in the javascript console, and no page loaded:
Error: uncaught exception: [Exception... "Component returned failure code:
0x804b0012 [nsIIOService.newURI]"  nsresult: "0x804b0012 (<unknown>)"  location:
"JS frame :: chrome://navigator/content/sessionHistoryUI.js ::
addToUrlbarHistory :: line 157"  data: no]

expected result:
load the page from the URL specified
using win2000, win32-installer build id 2001062104

workaround: ctrl+shift+L

Comment 1

[Alec Flett]

ok, this really is dougt's.
I'll try to investigate, but this looks like fallout from the standardurl
parsing junk.

Comment 2

[Alec Flett]

*** Bug 87280 has been marked as a duplicate of this bug. ***

Comment 3

[Blake Ross]

I'm pretty sure doug fixed this already.

Comment 4

[Eric Hedström]

Still happens with this morning's (06/22) win32-installer build.

Creating a new profile makes it work, but seeing as clearing the URL history
works too I suppose that's overkill.

Comment 5

[Chris Hiner]

Also, using a url with a port number, like bugzilla.mozilla.org:80, causes the
same error, except on line 141, and clearing the histories does NOT fix it.

Comment 6

[Doug Turner (:dougt)]

the url w/ a port number is an interesting one.  Given a 
string "www.example.com:80", nsIIOService::ExtractScheme thinks that the scheme 
is "www.example.com".  No default scheme will cause newURI to fail.
 

Comment 7

[Doug Turner (:dougt)]

I can not reproduce any other failure in the url bar beside typing a "url w/ a 
port number".  Is this bug reporting two problems?

Comment 8

[Eric Hedström]

Originally this bug (and its duplicates) were just for a plain hostname or URL
(e.g. I was trying www.suck.com) w/o the port number, but I haven't seen the
original error since creating a new user profile. Maybe I don't have enough
cruft in my history again yet, I don't know. I have a profile at home for which
this bug still exists, if I can give you any more useful information from that.

Comment 9

[Christos Cheretakis]

Using 2001062121 on linux and getting similar results.

When I write a URL that's in history list, hitting enter gets the page. After
appending a directory (eg /products/) mozilla completely ignores it. In my case,
it does not produce a message on the console eihter.

Comment 10

[Claudius Gayle]

either decide that this bug is just to address the case of using a port number or this bug
is a dupe of bug 87243.

Comment 11

[Doug Turner (:dougt)]

This bug is just to address the case of using a port number.  :-)

Comment 12

[basic]

*** Bug 87409 has been marked as a duplicate of this bug. ***

Comment 13

[Jacob Kjome]

If this bug is here only to address the case when using a port number, then 
niether bug 87280 nor bug 87409 should be a dup of this bug. Rather, they 
should be dups of bug 87243.

Also, here is the behavior I am seeing which I first noted in bug 86133 (read 
that bug to make sure you don't confuse this bug's behavior this that bug's 
behavior)...

the following URL pattern fails (note, this fails in IE5.5 too):

www.[some_valid_domain]:80/

where the following works fine:

http://www.[some_valid_domain]:80/


Jake

Comment 14

[Alec Flett]

*** This bug has been marked as a duplicate of 83489 ***

Comment 15

[Claudius Gayle]

Hmmm, I'm going to mark VERIFIED Dupe for now. We'll see after I verify the other fixes.