Closed
Bug 475913
Opened 16 years ago
Closed 16 years ago
nsIXULWindow interface changed withou changing uuid
Categories
(Core :: XUL, defect, P1)
Core
XUL
Tracking
()
VERIFIED
FIXED
People
(Reporter: pjemen, Assigned: bzbarsky)
References
Details
(Keywords: verified1.9.1)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 XPCOMViewer/1.0a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081210 Thunderbird/3.0b1
new method
void applyChromeFlags();
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvsroot&subdir=mozilla/xpfe/appshell/public&command=DIFF_FRAMESET&root=/cvsroot&file=nsIXULWindow.idl&rev1=1.16&rev2=1.17
Reproducible: Always
Actual Results:
old uuid
Expected Results:
new uuid
|
Reporter | |
Updated•16 years ago
|
Flags: wanted-thunderbird3?
Version: unspecified → Trunk
|
||
Updated•16 years ago
|
Blocks: 345560
Component: General → XUL
Flags: wanted-thunderbird3?
Product: Thunderbird → Core
QA Contact: general → xptoolkit.widgets
|
Assignee | |
Updated•16 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.9.1?
|
||
Comment 1•16 years ago
|
||
This happened prior to Firefox 3. Life sucks, but I don't think we can do anything about it now.
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: blocking1.9.1? → blocking1.9.1-
Resolution: --- → WONTFIX
|
|
Assignee | |
Comment 2•16 years ago
|
||
Reopening for now pending things being sorted out in .planning
Status: RESOLVED → REOPENED
Flags: blocking1.9.1- → blocking1.9.1?
Resolution: WONTFIX → ---
|
|
Assignee | |
Comment 3•16 years ago
|
||
Er, .platform
|
||
Updated•16 years ago
|
Assignee: nobody → bzbarsky
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P1
|
|
Assignee | |
Comment 4•16 years ago
|
||
Pushed http://hg.mozilla.org/mozilla-central/rev/3717bfa25bc9 and http://hg.mozilla.org/mozilla-central/rev/3717bfa25bc9
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Keywords: fixed1.9.1
Resolution: --- → FIXED
|
||
Comment 5•16 years ago
|
||
Seeing as there hasn't been any discussions about this bug for 2 months, I'm guessing there aren't any residual issues. I'm moving this to verified as a result. If anyone has any qualms, feel free to bring them up.
Status: RESOLVED → VERIFIED
Keywords: fixed1.9.1 → verified1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•