No "Theme changes will take effect[...]" after last window closed

RESOLVED INVALID

Status

Core Graveyard
Skinability
P3
minor
RESOLVED INVALID
17 years ago
9 years ago

People

(Reporter: odd@findus.dhs.org, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

Trunk
mozilla0.9.9
PowerPC
Mac System 9.x

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.3+) Gecko/20010810
BuildID:    2001081008

After having closed all browser, mail, et cetera windows and choosing View>Apply
Theme| <new theme>, one doesn't get the "Theme changes will take effect when you
restart Mozilla" dialog.

Reproducible: Always
Steps to Reproduce:
1. Open Mozilla
2. Close all windows
3. Select a new theme in the View>Apply Theme menu

Actual Results:  The proper theme alert dialog does not appear

Expected Results:  The proper theme alert dialog should appear
over to skinability
Assignee: hewitt → ben
Component: Themes → Skinability

Comment 2

17 years ago
Confirmed under Mac/2001080214 (0.9.3).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla0.9.7
Does the theme change at all? 
Hopefully we're going to fix dynamic skin switching during this release. 
Target Milestone: mozilla0.9.7 → mozilla0.9.9
(Reporter)

Comment 5

16 years ago
I wasn't complaining about dynamic skin switching not being there, but that no
dialogue alerting the user that it'll be applied on the next start appeared
after the last window had been closed.

Comment 6

16 years ago
Seeing this also in win32, its also not closing the quick launch task.
build 2001102309.
Is this heading towards having instant theme switching? Strange that its not all
landing at the same time. 
theme changes now happen dynamically
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.