Closed
Bug 124676
Opened 23 years ago
Closed 21 years ago
mac os x interface composer tabs too small
Categories
(SeaMonkey :: Themes, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: macmouse4, Assigned: shliang)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.8+)
Gecko/20020209
BuildID: 2002020903
The "Table Cell Properties" has some cosmotic problems when viewed in mac os x.
(using mac os x 10.2.1). Looks like the tabs are too small.
Reproducible: Always
Steps to Reproduce:
1.Make a new composer page
2. Make a table
3. bring the contextual menu down and select "Table Cell Properties"
Actual Results: It looks weird/abd
Expected Results: The menu should have a bit more space and bigger tabs. also
some text doesn't have an os x like background but the main thing is the tabs
(could prevent functionality).
a screen shot can be found at (http://homepage.mac.com/macmouse4/screen.gif)
*** Bug 125049 has been marked as a duplicate of this bug. ***
confirming, based on dup
Status: UNCONFIRMED → NEW
Ever confirmed: true
Steve, this isn't composer, could you assign appropriately?
Assignee: syd → sdagley
Component: Editor: Composer → XP Toolkit/Widgets
Target Milestone: --- → Future
Comment 5•23 years ago
|
||
In current trunk builds I don't see the whacked tabs so my inclination is to
mark it WORKSFORME. I suspect this was either a problem in the Classic theme or
during the transition to the native theme work pink was doing. I do see a
problem with the table cell properties dialog right now though - it comes up
with both tabs showing as active when using the Classic theme (Modern displays
correctly). Reassigning as a theme bug and cc:ing pinkerton.
Assignee: sdagley → shliang
Component: XP Toolkit/Widgets → Themes
QA Contact: sujay → pmac
Comment 6•21 years ago
|
||
worksforme with 2004020308 Mac SeaMonkey on 10.3
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•