Closed Bug 382795 Opened 18 years ago Closed 15 years ago

SeaMonkey Theme regressions post XUL app (suiterunner) switchover.

Categories

(SeaMonkey :: Themes, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Unassigned)

References

Details

(Keywords: fixed-seamonkey2.0, meta)

This is a meta bug for tracking theme regressions from the xul app (suiterunner) switchover.

Please don't post potential bugs here, just link them.
Flags: blocking-seamonkey2.0a1?
Depends on: 378545, 380641
Depends on: 379192
Depends on: 383532
Depends on: 384080
Blocks: 384185
No longer blocks: 384185
Depends on: 384185
Depends on: 384340
Depends on: 383870
Depends on: 384821
Depends on: 385252, 385254
Depends on: 386898
Depends on: 390058
Depends on: 382642
Depends on: 394635
Out of curiosity, the blocking request was set for over 3 months ago. Is there anyone looking at those requests?
(In reply to comment #1)
> Out of curiosity, the blocking request was set for over 3 months ago. Is there
> anyone looking at those requests?

I set the blocking request when I raised this bug, so that we wouldn't forget it when it when we come round to alpha, as some of the dependent bugs are quite significant.

As we still have a significant way to go (I believe) until we are ready for alpha (as we still want various items to transfer to toolkit), there's not too much point in looking at blocking requests at this stage. Anyway IMHO any discussion on this is much better on m.d.a.seamonkey rather than in bugs.
Depends on: 398078
Depends on: 398138
Depends on: 407048
Could you put the blocking on the significant dependent bugs and we'll push this one back as potentially blocking final.
Flags: blocking-seamonkey2.0a1? → blocking-seamonkey2?
Assignee: general → nobody
Component: General → Themes
QA Contact: general → themes
Flags: blocking-seamonkey2.0? → blocking-seamonkey2.0+
All dependent bugs fixed -> FIXED
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.