Closed Bug 172426 Opened 22 years ago Closed 21 years ago

Remove modern listing now that we don't package modern theme.

Categories

(Firefox :: Settings UI, defect)

Product:
Firefox
Component:
Settings UI
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 191992

People

(Reporter: rijken, Assigned: bugzilla)

References

Details

When selecting modern theme from preferences nothing changes. After restarting
Phoenix, the classic theme is still selected
morphing bug. 

Remove modern listing now that we don't package modern theme.
Status: UNCONFIRMED → NEW
Component: General → Preferences
Ever confirmed: true
OS: Linux → All
Summary: Themes don't change → Remove modern listing now that we don't package modern theme.
*** Bug 172617 has been marked as a duplicate of this bug. ***
and update the themes link to projects/phoenix/themes (or /extensions)
This seems like a real bug and there's no explanation to show why not.

Please see new bug 175968

*** Bug 175968 has been marked as a duplicate of this bug. ***
*** Bug 175968 has been marked as a duplicate of this bug. ***
This will just happen when we ditch wallet for good...

*** This bug has been marked as a duplicate of 171082 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
*** Bug 190836 has been marked as a duplicate of this bug. ***
I don't understand this.
18xxxxx JAR and XxI files don't install is marked resolved.
This bug, 172426, is marked resolved.
190836 is marked "duplicate" and resolved.
This shows "Remove modern listing now that we don't package modern theme."
Well, you still package "modern" theme. "Modern.jar" comes with Phoenix, Modern 
shows as an optional theme.
I also mentioned, in 190836, that Obit+3 doesn't install, yet there's no mention 
of that problem. Or of the fact that my "Classic" theme is actually "Qute."
This "themes not installing or not being correct" is a major problem and needs 
to be addressed as such! IMHO
Phoenix is good but it's a lot worse since late December - especially compared 
to November builds.
Now that bug 171082 is a meta bug, shouldn't this be a blocker rather than a dupe?
for good pointer
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
ben is working now

*** This bug has been marked as a duplicate of 191992 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 21 years ago
Resolution: --- → DUPLICATE
v.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.