Closed Bug 70149 Opened 24 years ago Closed 24 years ago

What's Related links don't load related sites

Categories

(SeaMonkey :: Sidebar, defect)

PowerPC
Mac System 9.x
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 57290

People

(Reporter: jeffrey, Assigned: matt)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; N; PPC; en-US; 0.8) Gecko/20010215 BuildID: What's Related links in SIDEBAR don't load related sites, they load other "what's related" reports in the SIDEBAR. For instance, visit http://www.alistapart.com/ and projectcool.com is listed as a related link. Click the projectcool.com link and projectcool.com should load in the browser window. Instead you get a listing of What's Related to ProjectCool. The browser window refreshes for no reason; the site in the browser window does not change. Reproducible: Always Steps to Reproduce: 1. Open Sidebar 2. Choose What's Related 3. Alexa database shows related sites 4. Click any related site. Actual Results: A new Alexa database fills the sidebar: the database that tells what's related to the site link you clicked. The related site does not load in the browser window. The browser window refreshes meaninglessly, but when it finishes refreshing what you see is the same site you started with. Not the site whose link you clicked. Expected Results: You expect to see the site whose link you clicked.
bug 57290 supposedly contains the what's related problem. If the url location bar updates to the site correctly, but the content of the site is not displayed in the main browser frame, then it's bug 57290. Else it's something else.
From my testing, this looks to be a dupe of bug 57290. The URL bar is correctly updating, the page just won't load. Marking a dupe, if you disagree, please reopen. *** This bug has been marked as a duplicate of 57290 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified in 3/5 build.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.