好吧,让我们举一个更合理的自定义协议处理程序示例。
我决定实现一个ddg: 协议处理程序,一旦注册,就可以在地址栏中输入ddg:some search terms(除其他外),它会加载 DuckDuckGo 搜索页面以查找“一些搜索词”。
组件
需要实现nsIProtocolHandler接口。
这个示例组件所做的是将“重定向”到 DuckDuckGo(好吧,不是真正的重定向,但它返回了一个用于 duckduckgo.com 的频道)。见内联 cmets。
var {classes: Cc,
interfaces: Ci,
manager: Cm,
results: Cr,
Constructor: CC
} = Components;
Cm.QueryInterface(Ci.nsIComponentRegistrar);
Components.utils.import("resource://gre/modules/Services.jsm");
Components.utils.import("resource://gre/modules/XPCOMUtils.jsm");
const SCHEME = "ddg";
const DDG_URI = Services.io.newURI("https://duckduckgo.com/?q=%s", null, null);
const nsIURI = CC("@mozilla.org/network/simple-uri;1", "nsIURI");
function DuckDuckGoProtocolHandler() {}
DuckDuckGoProtocolHandler.prototype = Object.freeze({
classDescription: "DuckDuckGo Protocol Handler",
contractID: "@mozilla.org/network/protocol;1?name=" + SCHEME,
classID: Components.ID('{858ea860-129a-11e4-9191-0800200c9a66}'),
QueryInterface: XPCOMUtils.generateQI([Ci.nsIProtocolHandler]),
// nsIProtocolHandler
scheme: SCHEME,
defaultPort: -1, // No default port.
// nsIProtocolHandler
allowPort: function(port, scheme) {
// This protocol handler does not support ports.
return false;
},
// nsIProtocolHandler
// Our protocol handler does not support authentication,
// but it is OK to be loaded from any web-page, not just privileged pages""
protocolFlags: Ci.nsIProtocolHandler.URI_NOAUTH |
Ci.nsIProtocolHandler.URI_LOADABLE_BY_ANYONE,
// nsIProtocolHandler
newURI: function(aSpec, aOriginCharset, aBaseURI) {
// Nothing special here, actually. We were asked to create a new URI.
// If there is a base-URI, this means that the browser tries to resolve
// a dependent resource (an image, script) or the user clicked on a relative link.
// In this case we cannot really return another "ddg" URI, but need to return
// the proper https URI.
if (aBaseURI && aBaseURI.scheme == SCHEME) {
return Services.io.newURI(aSpec, aOriginCharset, DDG_URI);
}
// We don't care about the charset, so just ignore that
// (we support what nsIURI supports).
let rv = new nsIURI();
rv.spec = aSpec;
return rv;
},
// nsIProtocolHandler
newChannel: function(aURI) {
// We were asked to open a new channel.
// We could implement an entirely custom channel that supports
// (most of) nsIChannel. But that is tremendous work and outside
// of the scope of this basic example (which is about protocol handlers and
// not channels).
// Or we can just return any other channel we can create.
// Since we're going to implement the "ddg:" protocol, lets just open a
// regular https channel to duckduckgo.com, use the URI as the search term
// and return that channel.
let spec = DDG_URI.spec.replace("%s", aURI.path);
let channel = Services.io.newChannel(spec, aURI.originCharset, null);
// Setting .originalURI will not only let other code know where this
// originally came from, but the UI will actually show that .originalURI.
channel.originalURI = aURI;
return channel;
}
});
chrome.manifest 中的组件注册
如果我们的组件是 JavaScript 组件,我们需要实现 NSGetFactory
通过 chrome.manifest 注册。幸运的是,XPCOMUtils.jsm 有一个帮手。
var NSGetFactory =
XPCOMUtils.generateNSGetFactory([DuckDuckGoProtocolHandler]);
在引导加载项(和 Scratchpad)中注册
在 bootstrapped/restartless 插件(包括 SDK 插件)和 Scratchpad 中,需要手动注册组件,因为 chrome.manifest 注册不可用。
可以注册NSGetFactory(classID)的结果,但这里有一些代码手动创建工厂并注册它。
function Factory(component) {
this.createInstance = function(outer, iid) {
if (outer) {
throw Cr.NS_ERROR_NO_AGGREGATION;
}
return new component();
};
this.register = function() {
Cm.registerFactory(component.prototype.classID,
component.prototype.classDescription,
component.prototype.contractID,
this);
};
this.unregister = function() {
Cm.unregisterFactory(component.prototype.classID, this);
}
Object.freeze(this);
this.register();
}
var factory = new Factory(DuckDuckGoProtocolHandler);
请注意,在无需重启的附加组件中,您还需要取消注册它
再次关机!
factory.unregister();
在 Scratchpad 中测试
将组件代码和手动注册代码复制到暂存器中,将Enviroment设置为Browser,然后运行。然后在标签中打开ddg:some search terms ;)