152798 - n7p1 can get so confused that whenever it finishes loading an http url it'll load a specific http url

Status: RESOLVED WONTFIX

(Core :: DOM: Navigation, defect)

Description

[timeless]

these are the only n7 xpi's i have:
 browser.zip deflenus.zip langenus.zip mail.zip psm.zip regus.zip skinclas.zip
 spellchk.zip talkback.zip xpcom.zip

steps: (not tested for reproducability)
run switcher2 (ask word about switcher.exe if you need it)
switch to deskstation 5 (an older switcher would call it 4, for some reason 
deskstation 2 isn't real, i'll ask pocemit)
run n7p1
i got profile manager
i picked another profile that hadn't been used in ages (i'm working my way up 
from the bottom of my profile list)
i went to edit>preferences
I disabled all the buttons except home and bookmarks
i disabled javascript (both navigator and mailnews)
i enabled syntax highlighting
i switched the search engine back to google
i verified that i was set to advanced search, don't pop out, and all 
autocomplete except match only.
i enabled load links in background (hide tabs was already enabled - from new 
features, this profile had never been used w/ a tab capable mozilla)
i disabled cookies
i disabled java
i ok'd out of prefs
i loaded in sequence:
[depth 2] a jpeg that tended to display poorly in mozilla (viewer, winembed) - 
it worked
[depth 1] the directory that was its parent - this kind of worked
i tried browsing the individual pictures there - this sometimes worked
[depth 0] i went to its parent
i tried following the links for the rest of the depth1's and their pictures, 
things weren't painting well
i went back to depth0 and /might/ have clicked on the last link which is the 
one that eventually got stuck in netscape's brain, it was kind of a 
[exitlink] default link for the remaining images

i then went back one more step, which should have led me to the netscape7p1 
start page.
i decided to give feedback, so i clicked the feedback link [this is the first 
site load where i noticed things went wonky]
the page loaded, but as soon as it finished, a new page [exitlink] loaded
this meant that my back/forward history had:
[exitlink]
http://channels.netscape.com/ns/browsers/7/feedback/default.jsp
http://channels.netscape.com/ns/browsers/7/default.jsp

i tried each of:
http://home.netscape.com/
http://www.netscape.com/
http://www.cnn.com/
as soon as they loaded, [exitlink] loaded
then i tried:
about:blank
about:
about:mozilla
-they loaded and nothing unusual happened
then i tried:
ftp://ftp.mozilla.org/pub/README
ftp://ftp.mozilla.org/pub/data/PerformanceAndFootprints.html
-they loaded and nothing bad happened (they didn't paint immediately, but some 
coercing got them to paint piecewise)

i tried creating a new window
http://wp.netscape.com/bookmark/7_0/home.html
-loaded (it's the default home page)
[exitlink] loaded shortly after i saw the beginning of it

i tried:
data:text/html,<iframe src="http://www.cnn.com">
[exitlink] loaded shortly after i saw the beginning of cnn
data:text/html,hi
-it loaded

somewhere i tried a new tab, but as soon as an http page loaded, i got 
[exitlink].

i have a copy of the history, but it's not quite the set of pages i'd like to 
distribute.

Comment 1

[Matthias Versen [:Matti]]

timeless: 
shouldn't you report this to the netscape feedback form ?
Or Do you see this with Mozilla ?

Comment 2

[timeless]

i'm going to pretend this happened in mozilla1.0rc2 and that the problem is 
still around today.  I can at some point try to write a fancy letter to the 
feedback thing but i doubt it will do much good.

Comment 3

[Michael Lefevre]

timeless - can you reproduce this, or is it destined to remain a "pretend" bug
forever? thanks.

Comment 4

[timeless]

ok, here's my guess: an onload handler was set to load [exitlink], and the only
protocol which fires onload is http. so the bug would be that an onload handler
persisted well beyond the page that set it.

Comment 5

[Matthias Versen [:Matti]]

timeless: Can you reproduce this with 1.4a or later builds ?

Comment 6

[Adam Lock]

Future. Is there an easier way, or any way still to reproduce this?

Comment 7

[Adam Lock]

Marking WONTFIX. If there is a reproducable :) way to see this behaviour in
recent builds, please reopen