Name Description Size
CLib.jsm 1684
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 38432
OTRHelpers.jsm 1142
OTRLib.jsm 30470
OTRUI.jsm probably imconv 25567
ToLocaleFormat.jsm 6516
hiddenWindow.jsm 771
imContentSink.jsm Tags whose content should be fully removed, and reported in the Error Console. 12740
imServices.jsm 1288
imSmileys.jsm Skip text nodes that contain the href in the child text node. We must check both the testNode.textContent and the aNode.data since they cover different cases: textContent: The URL is split over multiple nodes for some reason data: The URL is not the only content in the link, skip only the one node Check the class name to skip any autolinked nodes from mozTXTToHTMLConv. 4941
imStatusUtils.jsm 1876
imTextboxUtils.jsm 3936
imThemes.jsm 34702
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. 8391
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. 32031
moz.build 672
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 secInfo Users should "subclass" this object, i.e. set their .__proto__ to be it. And then implement: onConnection() onConnectionHeard() onConnectionTimedOut() onConnectionReset() onBadCertificate(boolean aIsSslError, 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. 20742
test 3