Closed Bug 475912 Opened 17 years ago Closed 17 years ago

nsITokenDialogs interface changed withou changing uuid

Categories

(Core :: Security: PSM, defect, P1)

Product:
Core
Component:
Security: PSM
Type:
defect

Tracking

()

Status:
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 displayProtectedAuth(in nsIInterfaceRequestor ctx, in nsIProtectedAuthThread runnable); http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvsroot&subdir=mozilla/security/manager/ssl/public&command=DIFF_FRAMESET&root=/cvsroot&file=nsITokenDialogs.idl&rev1=1.3&rev2=1.4 Reproducible: Always Actual Results: old uuid Expected Results: new uuid
Flags: wanted-thunderbird3?
Version: unspecified → Trunk
Assignee: nobody → kaie
Status: UNCONFIRMED → NEW
Component: General → Security: PSM
Ever confirmed: true
Flags: wanted-thunderbird3?
Product: Thunderbird → Core
QA Contact: general → psm
Flags: blocking1.9.1?
This happened prior to Firefox 3, and was released. Life sucks, but I don't think we shuold change things now.
Blocks: 119500
Status: NEW → RESOLVED
Closed: 17 years ago
Flags: blocking1.9.1? → blocking1.9.1-
Resolution: --- → WONTFIX
Reopening for now pending things being sorted out in .planning
Status: RESOLVED → REOPENED
Flags: blocking1.9.1- → blocking1.9.1?
Resolution: WONTFIX → ---
I meant .platform.
Assignee: kaie → bzbarsky
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P1
Pushed http://hg.mozilla.org/mozilla-central/rev/deed959ce4e5 and http://hg.mozilla.org/releases/mozilla-1.9.1/rev/ba616048fd4c
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Keywords: fixed1.9.1
Resolution: --- → FIXED
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.