Closed Bug 371190 Opened 19 years ago Closed 19 years ago

Some localized builds have broken migration wizards (missing the option to choose a homepage)

Categories

(Firefox :: Migration, defect)

2.0 Branch
defect
Not set
major

Tracking

()

RESOLVED FIXED
Firefox 2

People

(Reporter: tchung, Assigned: Gavin)

Details

(Keywords: verified1.8.1.4)

Attachments

(2 files)

Repro: 1) open IE, and save a few bookmarks, homepages 2) Download and install the Portal 2.0.0.1 zhTW build. Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-TW; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 3) blow away your appdata\Mozilla directory 4) run firefox.exe and watch the migration wizard appear. 5) Verify migration wizard is missing the option to choose a startup homepage. ** See attachment Expected: - option should appear to choose Portal homepage or IE homepage options Actual: - The dialog box has no options to choose anything.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Summary: PCHome migration wizard is missing the option to choose a homepage → PCHome migration wizard is missing the option to choose a homepage (ko and zh-TW, 2.0.0.x)
Per discussion with Gavin, I am reactivating this bug because this affects bug affects other locales that may have a broken migration Wizard. This was found origially for Portal20/PCHome 2.001 on zh-TW, but could very well affect any builds that have missing strings returned in the import dialog window (both 1.5x and 2.001) Related bug is bug 371155
Keywords: fixed1.8.1.2
Version: 2.0 Branch → Trunk
Status: RESOLVED → REOPENED
OS: Windows XP → All
Hardware: PC → All
Resolution: FIXED → ---
Summary: PCHome migration wizard is missing the option to choose a homepage (ko and zh-TW, 2.0.0.x) → Some localized builds have broken migration wizards (missing the option to choose a homepage)
Version: Trunk → 1.5.0.x Branch
Status: REOPENED → NEW
This also repros on the Divx 2.0 ko RC1 build.
Also seen this with the Google GooglePak ja build for 2.0.0.1. See attachment 2 [details] [diff] [review]
Group: mozillacomconfidential
Basil, timr: Is there any reason for this bug to be Mozilla Corp confidential?
This bug was fixed for 2.0.0.x by bug 371309, and I don't think we're going to be making any changes to the 1.5.0.x builds at this point, so marking this FIXED.
Status: NEW → RESOLVED
Closed: 19 years ago19 years ago
Keywords: fixed1.8.1.4
Resolution: --- → FIXED
Version: 1.5.0.x Branch → 2.0 Branch
(In reply to comment #6) > Basil, timr: Is there any reason for this bug to be Mozilla Corp confidential? > I think this is marked confidential as it affects how we broke specific partner distros and this had to be communicated to them very carefully. Best to leave it confidential IMO.
(In reply to comment #7) > This bug was fixed for 2.0.0.x by bug 371309, and I don't think we're going to > be making any changes to the 1.5.0.x builds at this point, so marking this > FIXED. > It doesn't look like this is needed for 1.5.0.x. Tony or Basil- do you disagree? I vote for marking it fixed.
I'm okay with leaving it fixed for 2.0.0.x only also.
(In reply to comment #8) > I think this is marked confidential as it affects how we broke specific partner > distros and this had to be communicated to them very carefully. As mentioned on IRC, this bug wasn't specific to partner builds, it just happened to be discovered while we were testing them.
Group: mozillacomconfidential
Verified fixes on zhTW and ko, 2004. option now appears in migWiz Mozilla/5.0 (Windows; U; Windows NT 5.1; ko; rv:1.8.1.4) Gecko/20070501 Firefox/2.0.0.4 Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-TW; rv:1.8.1.4) Gecko/20070501 Firefox/2.0.0.4
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: