Correct me if I'm wrong, Ben, but there should be no need to keep the unix classic theme in the tree. It hasn't been touched since I've been around Netscape, and I see no reason to keep it around.
FWIW, some of the files are loaded when I run -- I see CSS errors in them. See bug 65443.
The Makefile.in files in classic point to the unix folders. I was not aware that these files were included in the classic.jar file on unix, so I fear that just removing them may break stuff. I'll have to remove them all and then go through each one and make sure the windows equivalent works well.
Themes Triage Team nsbeta1+
Let me make sure I'm correct...what you call the "Unix classic theme", is actually the XFE theme before we switched to XPFE, right?
No, I think it was originally a branch off the Windows classic skin that nobody wanted to maintain, so it's still pretty similar to the Windows classic skin.
What about all the Unix-specific files?
The Unix-specific files are all in the unix directories that I listed in the patch. They will all be removed. They are not currently performing any function on the unix builds of the classic skin.
Oops sorry, I missed: "REMOVE ALL FILES UNDER ============= themes/classic/navigator/unix themes/classic/global/unix themes/classic/communicator/unix themes/classic/communicator/sidebar/unix" r=blake assuming you've built and tested this on linux.
r=timeless whack em
Keywords: review → approval
OS: All → Linux
Hardware: All → PC
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Marking verified (2001-02-13-09-Mtrunk)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.