Closed Bug 475915 Opened 16 years ago Closed 15 years ago

nsPIWindowWatcher interface changed without changing uuid

Categories

(Core Graveyard :: Embedding: APIs, defect, P1)

Product:
Core Graveyard
Component:
Embedding: APIs
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: pjemen, Assigned: bzbarsky)

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

nsPIWindowWatcher

 "in PRUint32 argc, in jsvalptr argv" changed to "nsIArray aArgs"

http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvsroot&subdir=mozilla/embedding/components/windowwatcher/public&command=DIFF_FRAMESET&root=/cvsroot&file=nsPIWindowWatcher.idl&rev1=1.11&rev2=1.12


Reproducible: Always

Actual Results:  
old uuid

Expected Results:  
new uuid
i forget:

chaged method name is: openWindowJS
Flags: wanted-thunderbird3?
Version: unspecified → Trunk
Component: General → DOM
Flags: wanted-thunderbird3?
Product: Thunderbird → Core
QA Contact: general → general
Component: DOM → Embedding: APIs
QA Contact: general → apis
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.9.1?
This is from bug 255942, and has been the same since mozilla 1.9a1. Not sure if there is much value in changing it since it hasn't changed since Firefox 3.
Flags: blocking1.9.1? → blocking1.9.1-
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
There's value for other Gecko-based apps (e.g. tbird).  We should probably sort this out in .planning before closing bugs, ok?
Status: RESOLVED → REOPENED
Flags: blocking1.9.1- → blocking1.9.1?
Resolution: WONTFIX → ---
I meant .platform.
Assignee: nobody → bzbarsky
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P1
Pushed http://hg.mozilla.org/mozilla-central/rev/03785cd2713a and
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/25463db6b41f
Status: REOPENED → RESOLVED
Closed: 16 years ago → 15 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
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.