8 Коммитов

Автор	SHA1	Сообщение	Дата
dmose%mozilla.org	9db590cec8	Fix web based protocol handlers to work from link clicks in addition to the URL bar (bug 383396), r=biesi, sr=sicking	2007-06-15 21:43:51 +00:00
dmose%mozilla.org	ea78346a1b	Implement backend changes for web-based protocol handlers a la WhatWG HTML5 draft (bug 380415). r=cbiesinger@gmx.at, sr=jonas@sicking.cc	2007-05-25 15:17:45 +00:00
bzbarsky%mit.edu	5bb05f7876	Blocked protocols should still allow URI creation; they should just fail ... channel creation. Bug 244220, r+sr=darin	2004-05-21 00:28:52 +00:00
gerv%gerv.net	aa835b77c5	Bug 236613: change to MPL/LGPL/GPL tri-license.	2004-04-17 16:52:41 +00:00
cbiesinger%web.de	f4f01b8b90	230970 ... nsExternalAppHandler needs no virtual functions also, w/o bug: nsExternalHelperAppService doesn't require threadsafe addref/release r=bzbarsky sr=darin	2004-01-16 18:22:55 +00:00
cavin%netscape.com	47ad5ffffc	Fix for 183111. Added nsIExternalProtocolHandler interface and method handlerExists in netwerk/bae/public to be used by mozTXTToHTMLConv. Also treated 0xA0 as space in mozTXTToHTMLConv. r=darin, sr=sspitzer.	2003-02-27 22:46:42 +00:00
mscott%netscape.com	fa94170c0b	Bug #63193 --> the external protocol handler should only return a url or a new channel if we really do ... have an external app that can handle the url. otherwise return NS_ERROR_UNKNOWN_PROTOCOL so we'll throw up an alert dialog later on. sr=sspizter	2001-02-07 05:24:27 +00:00
mscott%netscape.com	7a3ab1efac	Bug #63193 --> add these two new files for a default protocol handler which will kick urls out to the OS ... sr=rpotts	2001-02-07 01:21:58 +00:00