Name Description Size
CLib.jsm 1746
imContentSink.jsm Tags whose content should be fully removed, and reported in the Error Console. 13542
IMServices.jsm 1248
imSmileys.jsm Used to add smileys to the content of a textnode. 5052
imStatusUtils.jsm 1904
imTextboxUtils.jsm 844
imThemes.jsm 39453
imXPCOMUtils.jsm Creates an nsIScriptError instance and logs it. @param aModule string identifying the module within which the error occurred. @param aLevel the error level as defined in imIDebugMessage. @param aMessage the error message string. @param aOriginalError (optional) JS Error object containing the location where the actual error occurred. Its error message is appended to aMessage. 7826
InteractiveBrowser.jsm URL to redirect to for completion of the redirect. @type {string} 4685
jsProtoHelper.jsm Convert a socket's nsITransportSecurityInfo into a prplIAccount connection error. Store the nsITransportSecurityInfo and the connection location on the account so the certificate exception dialog can access the information. @param {Socket} aSocket - Socket where the connection error occurred. @returns {Number} The prplIAccount error constant describing the problem. 49902
moz.build 656
NormalizedMap.jsm A Map that automatically normalizes keys before accessing the values. The constructor takes two parameters: aNormalize: A function which takes a string and returns the "normalized" version of it. aIterable: A iterable to prefill the map with, keys will be normalized. Returns a Map object that will automatically run aNormalize on any operations involving keys. 1598
OTR.jsm @param {string} filename - File in the profile. @returns {string} Full path to given file in the profile directory. 41842
OTRLib.jsm 31051
OTRUI.jsm probably imconv 27760
socket.jsm Combines a lot of the Mozilla networking interfaces into a sane interface for simple(r) handling of a low-level socket which sends text content. This implements nsIStreamListener, nsIRequestObserver, nsITransportEventSink and nsIProtocolProxyCallback. This uses nsIRoutedSocketTransportService, nsIServerSocket, nsIThreadManager, nsIScriptableInputStream, nsIInputStreamPump, nsIProxyService, nsIProxyInfo. High-level methods: connect(<originHost>, <originPort>[, ("starttls" | "ssl" | "udp") [, <proxy>[, <host>, <port>]]]) disconnect() sendData(String <data>[, <logged data>]) sendString(String <data>[, <encoding>[, <logged data>]]) startTLS() resetPingTimer() cancelDisconnectTimer() High-level properties: delimiter inputSegmentSize outputSegmentSize proxyFlags connectTimeout (default is no timeout) readWriteTimeout (default is no timeout) disconnected securityInfo Users should "subclass" this object, i.e. set their .__proto__ to be it. And then implement: onConnection() onConnectionHeard() onConnectionTimedOut() onConnectionReset() onConnectionSecurityError(unsigned long aTLSError, optional AString aNSSErrorMessage) onConnectionClosed() onDataReceived(String <data>) onTransportStatus(nsISocketTransport <transport>, nsresult <status>, unsigned long <progress>, unsigned long <progress max>) sendPing() LOG(<message>) DEBUG(<message>) Optional features: The ping functionality: Included in the socket object is a higher level "ping" messaging system, which is commonly used in instant messaging protocols. The ping functionality works by calling a user defined method, sendPing(), if resetPingTimer() is not called after two minutes. If no ping response is received after 30 seconds, the socket will disconnect. Thus, a socket using this functionality should: 1. Implement sendPing() to send an appropriate ping message for the protocol. 2. Call resetPingTimer() to start the ping messages. 3. Call resetPingTimer() each time a message is received (i.e. the socket is known to still be alive). 4. Call cancelDisconnectTimer() when a ping response is received. 20510
test 7
ToLocaleFormat.jsm JS implementation of the deprecated Date.toLocaleFormat. aFormat follows strftime syntax, http://pubs.opengroup.org/onlinepubs/007908799/xsh/strftime.html 6816