Components are at incorrect location in "Select Typical/Additional Components" screen

VERIFIED FIXED in mozilla1.0

Status

P2
major
VERIFIED FIXED
17 years ago
17 years ago

People

(Reporter: jimmyu, Assigned: shrutiv)

Tracking

other
mozilla1.0
x86
Windows 2000

Details

(Whiteboard: [cckrtm+])

Attachments

(6 attachments)

(Reporter)

Description

17 years ago
When selected custom install with a customized build, the components are not 
in the correct places. See screen shot to follow.

Correct component locations ~
Screen ~ "Netscape 6 Setup - Select Typical Components"
         []Navigator
         []Mail & Instant Messaging
         []Spell Checker

SCreen ~ "Netscape 6 Setup - Select Additional Components"
         []Sun Java 2
           ...
           ...
         []Canadian region pack
(Reporter)

Comment 1

17 years ago
Created attachment 78649 [details]
Incorrect components location
(Assignee)

Updated

17 years ago
Priority: -- → P2
(Assignee)

Updated

17 years ago
Severity: critical → major

Comment 2

17 years ago
TM -> Future per triage
Target Milestone: --- → Future
(Reporter)

Comment 3

17 years ago
Created attachment 86089 [details]
Screen shot of core client Recommended install

The component list on the core client for Recommended install
(Reporter)

Comment 4

17 years ago
Created attachment 86090 [details]
Screen shot for CCK/NCADM client Recommended install

The component list on the CCK/NCADM client for Recommended install
(Reporter)

Comment 5

17 years ago
Created attachment 86092 [details]
Screen shot of core client Custom install

The component list on the core client for Custom install
(Reporter)

Comment 6

17 years ago
Created attachment 86093 [details]
Screen shot of CCK/NCADM client Custom install

The component list on the CCK/NCADM client for Custom install
(Reporter)

Comment 7

17 years ago
Please review the screenshots for core and CCK/NCADM client in regards to the
Recommended and Custom install.

In regards to Recommended install for CCK/NCADM client it does properly install
the recommended components as the core client, but in the "Additional
Componenets" screen it appears to be different with the core client.

As for the Custom install for CCK/NCADM client the "Components" and "Additional
Components" screens is completely in a different order. Plus the "Canadian
region pack" should not be checked.

This is not a very critical problem, but an end user experience issue that they
see when they install a customize client. Which I see this is a bad experience
for an end-user so I want to nominate this bug for cckrtm.

How can I nominate a bug for CCK RTM? For now I'll put cckrtm in the status
whiteboard if anyone feel that this shouldn't go in for RTM please feel free to
remove cckrtm from the status whiteboard.

Nominate cckrtm
Whiteboard: [ccktrtm]

Updated

17 years ago
Whiteboard: [ccktrtm] → [ccktrtm+]

Updated

17 years ago
Whiteboard: [ccktrtm+] → [cckrtm+]

Updated

17 years ago
Target Milestone: Future → mozilla1.0
(Assignee)

Comment 8

17 years ago
Created attachment 94694 [details] [diff] [review]
Proposed fix

The pacth displays the CCK customized component list for Custom install similar
to the core client. CCK was using 'Full install' (setup type 1) option, changed
it to custom install.
(Assignee)

Updated

17 years ago
Whiteboard: [cckrtm+] → [cckrtm+]need r=
Comment on attachment 94694 [details] [diff] [review]
Proposed fix

r=smeredith
(Assignee)

Comment 10

17 years ago
Checked into trunk and branch.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
Whiteboard: [cckrtm+]need r= → [cckrtm+]

Comment 11

17 years ago
load balance -> over to lrg
QA Contact: blee → lrg

Comment 12

17 years ago
Verified with the 20020812 NCADM and CCK builds
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.