Closed Bug 102736 Opened 23 years ago Closed 23 years ago

Can't edit prferences in classic skin

Categories

(Core Graveyard :: Skinability, defect)

PowerPC
Mac System 9.x
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tracy, Assigned: hewitt)

Details

(Keywords: regression)

seen on mac commercial build 2001-10-02-09-trunk

-launch in classic skin
-go to Edit | Preferences

the expected preferences dialogue does not pop up. nothing happens.

note:  swith to modern theme and this works fine.  other wise this would be 
smoketest blocker.  Or is theme switching an acceptable workaround?
eek!

samir, i don't have a recent mac 9.x trunk build handy...have you encountered
this yet?
gonna check the os x trunk...
->andreww?

methinks this ought to be a blocker --mainly since the default theme for new
profiles is classic-- at least in mac commercial trunk bits. i'm tempted even to
make this a smoketest blocker...however, feel free to re-prioritize since there
is a workaround.

as for mac os x trunk: well, the most recent trunk build is from
2001.09.30.20...does anyone have a more recent build to see if this is a problem
there? thx!
Assignee: ben → andreww
Severity: critical → blocker
Tracy, I just tried on Mac OS 9.2 (branch build: 2001-10-02-03-0.9.4) and it 
works fine. So maybe it only happens on the trunk build.
Severity: blocker → critical
resetting stuff, musta gotten clobbered by accident. :)
Severity: critical → blocker
Patty, yes it's just trunk.  Branch builds were fine this morning.
Tracy, yes, I just tried on the Mac OS 9.2 (trunk build: 2001-10-02-09-trunk),
the expected preferences dialogue does not pop up. However, it pops up 
in modern skin though.
ok Joe did it with his dialog checkin. reassigning.
Assignee: andreww → hewitt
chrome://global/skin/dialog.css is missing in Mac classic.
fixed
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
verified on mac commercial build 2001-10-03-04-trunk
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.