gecko-dev/uriloader/base/nsIContentHandler.idl
mscott%netscape.com 333edb2c69 Bug #30553 --> new windows with window targets were getting the target associated with the
chrome window instead of with the content window. And the window sizes were coming from the
	       hidden window instead of the parent window the url originated from.
r=travis
a=jevering
2000-03-09 08:17:40 +00:00

42 lines
1.6 KiB
Plaintext

/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 4 -*-
*
* The contents of this file are subject to the Netscape Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of
* the License at http://www.mozilla.org/NPL/
*
* Software distributed under the License is distributed on an "AS
* IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
* implied. See the License for the specific language governing
* rights and limitations under the License.
*
* The Original Code is mozilla.org code.
*
* The Initial Developer of the Original Code is Netscape
* Communications Corporation. Portions created by Netscape are
* Copyright (C) 1999 Netscape Communications Corporation. All
* Rights Reserved.
*
* Contributor(s):
*/
#include "nsISupports.idl"
interface nsIChannel;
[scriptable, uuid(2F0F927A-8677-11d3-989D-001083010E9B)]
interface nsIContentHandler : nsISupports
{
/* HandleContent works as the name implies =).
aSourceContext --> The context associated with the originator of the content we are
trying to display. When is this typically used? Well, if handle
content needs to create a new window in order to display the content,
it needs to know about the dom window where the content originated from.
aChannel is an open channel whose content type is already known (aContentType) */
void handleContent(in string aContentType,
in string aCommand,
in string aWindowTarget,
in nsISupports aSourceContext,
in nsIChannel aChannel);
};