Missing buttons on the menu bar

VERIFIED WORKSFORME

Status

SeaMonkey
UI Design
VERIFIED WORKSFORME
17 years ago
13 years ago

People

(Reporter: Daniel, Assigned: Paul Chen)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
The system is missing the File, Edit, and the next button on the menu bar. The
pull-down menus will still appear, but no text or button on the menu bar. 

OS Caldera 2.4.2 Nightly build downloaded on 10/09/01.

Comment 1

17 years ago
Which theme are you using? This has been seen to happen when incompatible themes
are used, or with old profiles. Does it happen with a clean profile too?

A workaround to try clean it out without a new profile may be to
exit mozilla, cd .mozilla/Default/<salt> and delete localstore.rdf and all under
chrome/

Other bugs about the same are plentiful... bug 88551, bug 84337, bug 102593 
xp apps
Assignee: attinasi → pchen
Component: Layout → XP Apps
QA Contact: petersen → sairuh

Comment 3

17 years ago
Mailed Daniel a walkthrough regarding first time installation and how to create
a new profile. He replied:

"A proper installation seems to have worked. Thank you. The menu bar is working
correctly and the creation of new messages is working as of this time. i will
watch it and report back if there are any problems."

Resolving as WFM.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]

b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.