Closed Bug 91585 Opened 24 years ago Closed 24 years ago

Startup URL shows up on every browser launch (branch only)

Categories

(SeaMonkey :: General, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: racham, Assigned: racham)

Details

(Whiteboard: [PDT+] fixed on branch)

Attachments

(3 files)

Here is what I noticed with build [ 2001-07-19-05-0.9.2 0 07/19/01 06:44:00 am directory] I downloaded from sweetlou. Case I : 1. Create a new profile 2. Activation window comes up. 3. Click on 'x' on the right upper corner to close the activation window 4. Browser window comes up 5. The startpage url is "http://home.netscape.com/browsers/6/su_setup61pr.html" 6. Close the browser window 7. Launch browser again 8. Click on 'x' of the activation window 9. Note that browser comes up with "http://home.netscape.com/browsers/6/su_setup61pr.html" again 10. It happens on every subsequent launches (repeating these steps) Case II : 1. Create a new profile 2. Activation window comes up 3. Activate without clicking on any links on activation window 4. Activation window closes 5. Browser window comes up 6. The startpage url is "http://home.netscape.com/browsers/6/su_setup.html" 7. Close the browser window 8. Launch browser again. 9. Note that browser comes up with "http://home.netscape.com/browsers/6/su_setup.html" again 10. It happens on every subsequent launches Let me know if you can reproduce the above scenarios...
and this happens in mozilla also from what I noticed with my debug build.. In your mozilla build, 1. Create a new profile 2. Browser launches with http://www.mozilla.org/mozorg.html 3. Close the browser 4. Launch it again 5. Browser is launched with http://www.mozilla.org/mozorg.html again Even If I visit some other site without closing the browser immediately, browser still goes back to http://www.mozilla.org/mozorg.html on the next launch In case of mozilla, on subsequent launches we should be going to http://www.mozilla.org. In case of commercial builds, on subsequent launches we should be going to http://home.netscape.com. Assinging this to Steve Morse as I think the fix in bugscape bug 4428 might have caused this.
Bhuvan - can you confirm your hypothesis by backing the change in bugscape 4428 out in your local tree and trying again? that would help greatly in narrowing it down!
grace - do you see this also?
QA Contact: doronr → gbush
marking PDT+ per PDT email.
Whiteboard: [PDT+]
I am updating my branch build. Once that is done, I can try backing out changes made in bugscape bug 4428.
I see it using Bhuvan's steps- using build 2001072006 on Win (also see different pages since/when I test links on Activation)
Steve is going to be out of the office. Bhuvan can you own this item since we need urgent coverage on it. ->racham
Assignee: morse → racham
Bugscape bug 7443 also uses this patch as part of solving startpage problems. Jag, Seth, Vishy, please review the patch in here. thanks bhuvan
r=jag
Bhuvan, looking at the two matrices, it seems like this only changes the behavior of the new profile. I assume 7443 is required to get fully correct behavior?
Whiteboard: [PDT+] → [PDT+] need sr=
Yes. that's right. Cases where user activates/cancels activation without clicking any link on activation window for a new a profile are the improvements here. Patch in bugscape bug 7443, improves the behavior further by doing the right thing when user clicks on links activation window. In bug 7443, I did mention the single case where we don't show the first page (i.e., clicking on a link on activation window and then closing the activation window using 'x') as we don't get a chance to make app visit the patch in that bug. So, jag is trying to come up with a solution which can take care of all cases where user clicks on a link on activation window.
sr=blake
Whiteboard: [PDT+] need sr= → [PDT+]
I just checked this in on the branch. According to the summary this is branch-only, but didn't morse's fix go on the trunk too?
Whiteboard: [PDT+] → [PDT+] fixed on branch
marking this fixed. this patch does not need to be applied to the trunk because the original apprunner changes were never put on the trunk.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Bhuvan, Jag, Blake - thanks to you all for fixing this problem. GREAT WORK!
Blake, Thanks for super-review and checking it in. I posted this same update yesterday around 17:30. Looks like the next screen was login and password, so that is missed. So, typing this again. I planned on doing checkins yesterday evening and when I checked my mail, I realized that you covered the checkin. Thanks again for taking care of this. Thanks to all those who helped us solving this bug. bhuvan
verifying on branch builds 200107230x (Win/Mac/Linux)
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: