84041 - Difference in default skin of mozilla vs. NS6 causing problems

Status: RESOLVED DUPLICATE of bug 101968

(Core Graveyard :: RDF, defect)

Description

[Grace Bush]

Steps to reproduce:
1. Install mozilla- test/verify profile bug
2. Install Netscape 6 (branch build for 6/4) and run with same profile

Actual results: Icons across top of browser are messed up
See attachment to follow

Expected results: No change in browser appearance

* workaround is to clean system and remigrate profile or create new profile in 
Netscape 6

Conrad,
I'm not sure where this should be assigned.  People in house have reported 
profiles being corrupted but could not specify what  might have caused. Since I 
was using Mozilla today to verify some profile bugs - and then installed branch 
build soon after- this was very evident.  I can reproduce at will :(
I'm not sure many folks will run into- but it is one cause for those corrupted 
profiles

Comment 1

[Marcia Knous [:marcia]]

I have experienced a similar problem to the one Grace is reporting, but in my 
case I migrated my profile from Communicator 4.x to N6.  I experienced the same 
problem with the buttons being messed up, and when I created a new profile the 
browser worked like a charm.   

Comment 2

[Conrad Carlen (not reading bugmail)]

Looking at it. I suspect it may have to do with differences in chrome between
NS6 and mozilla. For the steps to reproduce, in step 1, did you make a new
profile or start with an existing one? Was anything migrated?

Comment 3

[Grace Bush]

In the first case I used a migrated 4.x profile (my own) - I then tried 
migrating a test profile and with a new profile.  All got corrupted- I did not 
investigate further except for Mail- those icons/buttons were ok. It was mainly 
the browser

Comment 4

[Grace Bush]

see bug 86807 for similar behavior noted...using profiles created in 6.0 or 6.01 
as well as mozilla

Comment 5

[Conrad Carlen (not reading bugmail)]

It's not exactly profile corruption, but chrome differences between NS6 and
mozilla. Changing summary. The default skin of NS6 is modern, whereas with
mozilla it's classic. Try this:
 
1. Make a new profile with NS6 (skin will be modern) and look at
<ProfileDir>/chrome/user-skins.rdf
2. Make a new profile with mozilla (skin will be classic), apply the modern
skin, and look at <ProfileDir>/chrome/user-skins.rdf for this profile.

The two user-skins.rdf files will be quite different. Hyatt, is this the
problem? What can we can do about it?

Comment 6

[Conrad Carlen (not reading bugmail)]

Whoops - it would help if I actually CC'd hyatt.

Comment 7

[Conrad Carlen (not reading bugmail)]

I don't think this is a profile mgr problem - probably chrome registry.

Comment 8

[Chris Waterson]

This is not likely to be a problem with RDF, or the chrome registry. It's
probably a result of the way they're being used: some bizarre divergence between
the Netscape6 and Mozilla trees. I'll keep the bug for now, but I don't know
when I'll have a chance to look at it.

Comment 9

[Boris Zbarsky [:bzbarsky]]

*** Bug 108349 has been marked as a duplicate of this bug. ***

Comment 10

[nrg]

The easiest solution would be to change the default mozilla skin from classic to
modern.  This would be the logical thing to do since NS6 is based on Mozilla.

Comment 11

[benc]

tever is not RDF QA anymore

Comment 12

[Andreas Kunz]

Dup of "clodern" bug 101968 (reported later, but much more attention).

*** This bug has been marked as a duplicate of 101968 ***