embedding/browser/webBrowser/nsIWebBrowserChrome.idl interface status

VERIFIED INVALID

Status

SeaMonkey
General
P3
normal
VERIFIED INVALID
18 years ago
13 years ago

People

(Reporter: Dawn Endico, Assigned: Dawn Endico)

Tracking

({arch})

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

18 years ago
Invitation for public comment on this Mozilla API.

Comment 1

18 years ago
This is porkjockey work that technically is not required by beta 1.  Moving to
M15.

Comment 2

18 years ago
Move to M16.
Target Milestone: M15 → M16
(Assignee)

Comment 3

18 years ago
Giving up on per IDL file review. Architecture product is going away.
Moving to Browser product and adding arch keyword, marking invalid.
Assignee: travis → endico
Status: ASSIGNED → NEW
Component: DocShell → Browser-General
Keywords: arch
Product: Architecture → Browser
Target Milestone: M16 → ---
Version: 5.0 → other
(Assignee)

Comment 4

18 years ago
Giving up on per IDL file review. Architecture product is going away.
Moving to Browser product and adding arch keyword, marking invalid.
(Assignee)

Comment 5

18 years ago
marking invalid
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID

Comment 6

18 years ago
*spam* changing qa contact from nobody@mozilla.org to me (BlakeR1234@aol.com) 
on 121 open or resolved (but not verified) bugs.  sorry for the spam everybody, 
but most of these bugs would just remain dormant and not checked by QA 
otherwise.  I'm not sure how so many bugs have nobody as their QA contact, but 
I suspect this is the fault of some sort of bugzilla corruption that happened 
at some point (most of these bugs are in the 20000-26000 range, and I don't see 
where in the activity log that QA contact explicitly changed to 
nobody@mozilla.org)

Anyways, sorry again for spam.  If you really get annoyed, I'm usually 
available in #mozilla on IRC for torture.
QA Contact: nobody → BlakeR1234

Comment 7

18 years ago
vrfy invalid...
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.