Index - Web APIs
e events. 643 clipboardevent.clipboarddata api, clipboard api, clipboardevent, experimental, method, read-only the clipboardevent.clipboarddata property holds a datatransfer object, which can be used: 644 closeevent api, interface, reference, web, websocket, websockets a closeevent is sent to clients using websockets when the connection is closed. this is delivered to the listener indicated by the websocket object's onclose attribute. 645 closeevent() api, closeevent, constructor, reference the closeevent() constructor creates a new closeevent. 646 closeevent.initcloseevent() the closeevent.initcloseevent() method initializes the value of a close event once it's been created (normally using the document.createevent...
...arget object instance. 1275 eventtarget.addeventlistener() api, accessouterdata, dom, detecting events, event handlers, event listener, eventtarget, javascript, method, passingdata, receiving events, reference, addeventlistener, attachevent, events, mselementresize the eventtarget method addeventlistener() sets up a function that will be called whenever the specified event is delivered to the target. 1276 eventtarget.attachevent() no summary! 1277 eventtarget.dispatchevent() api, dom, dom element methods, gecko, method dispatches an event at the specified eventtarget, (synchronously) invoking the affected eventlisteners in the appropriate order. the normal event processing rules (including the capturing and optional bubbling phase) als...
...vent, property, reference the onpointerenter property of the globaleventhandlers mixin is an eventhandler that processes pointerenter events. 1531 globaleventhandlers.onpointerleave api, globaleventhandlers, html dom, needsbrowsercompatibility, pointer events, pointerevent, property, reference, onpointerleave the global event handler for the pointerleave event, which is delivered to a node when the pointer (mouse cursor, fingertip, etc.) exits its hit test area (for example, if the cursor exits an element or window's content area). this event is part of the pointer events api. 1532 globaleventhandlers.onpointermove api, event handler, globaleventhandlers, html dom, pointerevent, property, reference the onpointermove property of the globaleventhandlers...
...And 5 more matches

Using DTMF with WebRTC - Web APIs
as packets alongside the track's audio data. each time a tone is sent, the rtcpeerconnection receives a tonechange event with a tone property specifying which tone finished playing, which is an opportunity to update interface elements, for example. when the tone buffer is empty, indicating that all the tones have been sent, a tonechange event with its tone property set to "" (an empty string) is delivered to the connection object. if you'd like to know more about how this works, read rfc 3550: rtp: a transport protocol for real-time applications and rfc 4733: rtp payload for dtmf digits, telephony tones, and telephony signals. the details of how dtmf payloads are handled on rtp are beyond the scope of this article. instead, we'll focus on how to use dtmf within the context of an rtcpeerconnection...
...s a fallback to let older browsers (and those not yet updated to support the current webrtc dtmf api) run the example. finally, we set the dtmf sender's ontonechange event handler so we get notified each time a dtmf tone finishes playing. you can find the log function at the bottom of the documentation. when a tone finishes playing each time a dtmf tone finishes playing, a tonechange event is delivered to callerpc. the event listener for these is implemented as the handletonechangeevent() function. function handletonechangeevent(event) { if (event.tone !== "") { log("tone played: " + event.tone); } else { log("all tones have played. disconnecting."); callerpc.getlocalstreams().foreach(function(stream) { stream.gettracks().foreach(function(track) { track.stop(); ...
...cdtmfsender object we previously stored in dtmfsender. our call to insertdtmf() specifies not only the dtmf to send (dialstring), but also the length of each tone in milliseconds (400 ms) and the amount of time between tones (50 ms). negotiating the connection when the calling rtcpeerconnection begins to receive media (after the microphone's stream is added to it), a negotiationneeded event is delivered to the caller, letting it know that it's time to start negotiating the connection with the receiver. as previously mentioned, our example is simplified somewhat because we control both the caller and the receiver, so handlecallernegotiationneeded() is able to quickly construct the connection by chaining the required calls together for both the caller and receiver, as shown below. function handle...
...ject from the event.candidate string and deliver it to the caller by passing that into callerpc.addicecandidate(). if addicecandidate() fails, the catch() clause outputs the error to our log box. if event.candidate is null, that indicates that there are no more candidates available, and we log that information. adding media to the receiver when the receiver begins to receive media, an event is delivered to the receiver's rtcpeerconnection, receiverpc. as explained in starting the connection process, the current webrtc specification uses the track event for this, but some browsers haven't been updated to support this yet, so we also need to handle the addstream event. the handlereceivertrackevent() and handlereceiveraddstreamevent() methods, shown below, handle these. function handlereceivertrac...

NPP_NewStream - Archive of obsolete content
er. the plugin should set this value to request a mode for the stream. for more information about each of these values, see directions in this section. np_normal (default): delivers stream data to the instance in a series of calls to npp_writeready and npp_write. np_asfileonly: saves stream data to a file in the local cache. np_asfile: file download. like np_asfileonly except that data is delivered to the plug-in as it is saved to the file (as in mode np_normal). np_seek: stream data randomly accessible by the plug-in as needed, through calls to npn_requestread. implementation note: some plugins, notably silverlight, do not set this outparam, and rely on the outparam being initialized to a default np_normal value. returns if successful, the function should return nperr_no_error...
... the browser calls npp_streamasfile to deliver the path of the file to the plug-in. if the stream comes from a local file, the npp_write and npp_writeready functions are not called. npp_streamasfile is simply called immediately. this mode allows the plug-in full random access to the data using platform-specific file operations. np_asfile: file download. differs from np_asfileonly in that data is delivered to the plug-in, through a series of calls to npp_writeready and npp_write, as it is saved to the file (as in mode np_normal). when the stream is complete, the browser calls npp_streamasfile to deliver the path of the file to the plug-in. if the data in the stream comes from a file that is already local, the data is read, sent to the plug-in through npp_write, and written to a file in the local ca...
...e file to the plug-in. if the data in the stream comes from a file that is already local, the data is read, sent to the plug-in through npp_write, and written to a file in the local cache. note: most plug-ins that need the stream saved to a file should use the more efficient mode np_asfileonly (above); this mode is preserved for compatibility only. np_seek: stream data is not automatically delivered to the instance, but can be randomly accessed by the plug-in as needed, through calls to npn_requestread. if the stream is not seekable, placing the stream in np_seek mode causes the browser to save the entire stream to the disk cache. npn_requestread requests are only fulfilled when all data has been read and stored in the cache. as an optimization to extract the maximum benefit from existing ne...

Index
use while offline. it includes methods for adding resources to and removing resources from the cache, as well as for enumerating the dynamically managed resource list. 510 nsidomorientationevent acceleration, dom, gecko 1.9.2, interfaces, interfaces:scriptable, mobile, orientation, xpcom interface reference the nsidomorientationevent interface describes the event that can be delivered to dom windows, providing information from the device's accelerometer, allowing code to determine the orientation of the device. 511 nsidomparser to create a domparser object from a web page or a chrome script running in a window, simply use new domparser(). when you create a domparser from a privileged script, you can pass parameters to the constructor, more on that below. ...
...istenermanager interfaces, interfaces:scriptable, message manager, xpcom, xpcom interface reference implemented by: @mozilla.org/globalmessagemanager;1. to access this service, use: 743 nsimessagesender message senders enable clients to send asynchronous messages to a single "other side". for example, a child-process message manager will send messages that are only delivered to its one parent-process message manager. 744 nsimessagewakeupservice interfaces, xpcom interface reference the parentprocessmessagemanager is used for this, so messages send from childprocessmessagemanagers will be heard. 745 nsimessenger interfaces, interfaces:scriptable, messages, needscontent, xpcom api reference, xpcom interface reference, thunderbird ...
...e. this will compute the key and expand the key to two keys, an aes256 encryption key and a 256 bit hmac key. it returns a key confirmation value (sha256d of the key) and the encryption and hmac keys. 993 nsisyncmessagesender message "senders" have a single "other side" to which messages are sent. for example, a child-process message manager will send messages that are only delivered to its one parent-process message manager. 994 nsitxttohtmlconv html, interfaces, interfaces:scriptable, xpcom interface reference prior versions of the interface named the methods using the initialcaps style instead of the intercaps style. 995 nsitaggingservice interfaces, interfaces:scriptable, places, xpcom, xpcom api reference, xpcom interface reference ...

Signaling and video calling - Web APIs
server supports several message types to handle tasks, such as registering new users, setting usernames, and sending public chat messages. to allow the server to support signaling and ice negotiation, we need to update the code. we'll have to allow directing messages to one specific user instead of broadcasting to all connected users, and ensure unrecognized message types are passed through and delivered, without the server needing to know what they are. this lets us send signaling messages using this same server, instead of needing a separate server. let's take a look which changes we need to make to the chat server support webrtc signaling. this is in the file chatserver.js. first up is the addition of the function sendtooneuser(). as the name suggests, this sends a stringified json message t...
...is means our signaling messages will be in json format, with contents which specify what kind of messages they are as well as any additional information needed in order to handle the messages properly. exchanging session descriptions when starting the signaling process, an offer is created by the user initiating the call. this offer includes a session description, in sdp format, and needs to be delivered to the receiving user, which we'll call the callee. the callee responds to the offer with an answer message, also containing an sdp description. our signaling server will use websocket to transmit offer messages with the type "video-offer", and answer messages with the type "video-answer". these messages have the following fields: type the message type; either "video-offer" or "video-answer".
...candidate", target: targetusername, candidate: event.candidate }); } } this builds an object containing the candidate, then sends it to the other peer using the sendtoserver() function previously described in sending messages to the signaling server. the message's properties are: type the message type: "new-ice-candidate". target the username the ice candidate needs to be delivered to. this lets the signaling server route the message. candidate the sdp representing the candidate the ice layer wants to transmit to the other peer. the format of this message (as is the case with everything you do when handling signaling) is entirely up to you, depending on your needs; you can provide other information as required. note: it's important to keep in mind that the icecandidat...

Web security
ured record of issued tls certificates. mixed content an https page that includes content fetched using cleartext http is called a mixed content page. pages like this are only partially encrypted, leaving the unencrypted content accessible to sniffers and man-in-the-middle attackers. how to fix a website with blocked mixed content if your website delivers https pages, all active mixed content delivered via http on these pages will be blocked by default. consequently, your website may appear broken to users (if iframes or plugins don't load, etc.). passive mixed content is displayed by default, but users can set a preference to block this type of content, as well. this page explains what you should be aware of as a web developer. secure contexts a secure context is a window or worker for which...
...quently, your website may appear broken to users (if iframes or plugins don't load, etc.). passive mixed content is displayed by default, but users can set a preference to block this type of content, as well. this page explains what you should be aware of as a web developer. secure contexts a secure context is a window or worker for which there is reasonable confidence that the content has been delivered securely (via https/tls), and for which the potential for communication with contexts that are not secure is limited. many web apis and features are accessible only in a secure context. the primary goal of secure contexts is to prevent man-in-the-middle attackers from accessing powerful apis that could further compromise the victim of an attack. features restricted to secure contexts this refer...
... policy is a critical security mechanism that restricts how a document or script loaded from one origin can interact with a resource from another origin. it helps isolate potentially malicious documents, reducing possible attack vectors. subresource integrity subresource integrity (sri) is a security feature that enables browsers to verify that resources they fetch (for example, from a cdn) are delivered without unexpected manipulation. it works by allowing you to provide a cryptographic hash that a fetched resource must match. http access-control-allow-origin the access-control-allow-origin response header indicates whether the response can be shared with requesting code from the given origin. http x-content-type-options the x-content-type-options response http header is a marker used by t...

context-menu - Archive of obsolete content
ray of content scripts associated with the menu item during creation. contentscriptfile the url of a content script or the array of such urls associated with the menu item during creation. events message if you listen to this event you can receive message events from content scripts associated with this menu item. when a content script posts a message using self.postmessage(), the message is delivered to the add-on code in the menu item's message event. arguments value : listeners are passed a single argument which is the message posted from the content script. the message can be any json-serializable value. menu a labeled menu item that expands into a submenu. methods additem(item) appends a menu item to the end of the menu. if the item is already contained in another menu or in the to...
... or the array of content scripts associated with the menu during creation. contentscriptfile the url of a content script or the array of such urls associated with the menu during creation. events message if you listen to this event you can receive message events from content scripts associated with this menu item. when a content script posts a message using self.postmessage(), the message is delivered to the add-on code in the menu item's message event. arguments value : listeners are passed a single argument which is the message posted from the content script. the message can be any json-serializable value. separator a menu separator. separators can be contained only in menus, not in the top-level context menu. methods destroy() permanently removes the separator from its parent menu an...

widget - Archive of obsolete content
ated widgetview object. click this event is emitted when the widget is clicked. arguments widgetview : listeners are passed a single argument which is the widgetview that triggered the click event. message if you listen to this event you can receive message events from content scripts associated with this widget. when a content script posts a message using self.postmessage(), the message is delivered to the add-on code in the widget's message event. arguments value : listeners are passed a single argument which is the message posted from the content script. the message can be any json-serializable value. mouseover this event is emitted when the user moves the mouse over the widget. mouseout this event is emitted when the user moves the mouse away from the widget. widgetview represents...
...the widget view is removed from its related window. this can occur if the window is closed, firefox exits, or the add-on is disabled. click this event is emitted when the widget view is clicked. message if you listen to this event you can receive message events from content scripts associated with this widget view. when a content script posts a message using self.postmessage(), the message is delivered to the add-on code in the widget view's message event. arguments value : listeners are passed a single argument which is the message posted from the content script. the message can be any json-serializable value. mouseover this event is emitted when the user moves the mouse over the widget view. mouseout this event is emitted when the user moves the mouse away from the widget view. ...

Extension Versioning, Update and Compatibility - Archive of obsolete content
infourl entry to the update manifest (see the example above). the page at this url will be retrieved and displayed to the user. since it is being displayed outside of a normal webpage context it is heavily sanitized, which means there are few formatting options available and scripting and images aren't allowed. the information page retrieved must currently be totally valid xhtml, including being delivered with the mime type application/xhtml+xml (important: see problems section) you may include %app_locale% in your updateinfourl if you want to have locale information included in the url -- this allows you to customize the text based on the user's locale. you may also use the other substitution strings supported by updateurl, although those may be less useful. formatting prior to firefox 4 prior...
...eurl uses https, or there is no updateurl at all (which defaults to addons.mozilla.org which is https) the updateurl uses http and the updatekey entry is specified which will be used to verify the data in the update manifest. when you specify an updatekey in the install.rdf, you must include a digital signature in the update manifest or the information will be rejected. in the update manifest delivered from the updateurl the updatelink must be specified in one of the following ways: the updatelink to the xpi file must use https the updatelink can use http and you must include an updatehash for the xpi file using sha1, sha256, sha384 or sha512 hash algorithms. any entries in the update manifest that do not meet one of those two requirements will be ignored when checking for new versions. ...

Index - Archive of obsolete content
use python code (almost) anywhere you can use javascript. 622 rdf api no summary! 623 rdf datasource how-to rdf no summary! 624 reading textual data add-ons, extensions, internationalization, unicode this article describes how to read textual data from streams, files and sockets. 625 remote xul xul how to use xul delivered from a webserver, not as part of chrome. 626 remote debugging when a bug is reproducible by a community member, but not on a developer's computer, a last-resort strategy is to debug it on the community member's computer. the crash victim should at least know how to run a debugger, if not how to use it, and should have a debug build of firefox handy. 627 remotely d...
... today's web browsers offer somewhat limited graphics capabilities to web developers. advances in hardware, especially graphics processors, offer the potential for far richer graphics in interactive applications. to realize this potential in web applications, browsers must expose rich new graphics apis to web content. the mozilla project will meet this challenge with two major new features to be delivered in firefox 1.5: integrated svg and a new canvas html element. work is also underway "under the hood" on a new unified graphics architecture that uses 3d graphics processors to accelerate all rendering. this work provides additional benefits to web developers such as the ability to apply svg effects to html content. 746 xul - mozilla's xml user interface language presentations, xul ...

Unix stub installer - Archive of obsolete content
n it by typing "gdb mozilla-installer-bin" on the shell prompt. how we get setup to debug the xpinstall engine from the unix stub installer? build your entire mozilla tree (which should build the installer in the src2 directory as well). go to mozilla/xpinstall/packager/unix. on the shell prompt type "perl deliver.pl". now you will find an installer *and* the xpcom.xpi and other debug xpis delivered to mozilla/installer/raw. debug using "gdb mozilla-installer-bin" and set a breakpoint at xpi_init(). you can step into the xpinstall engine through the xpistub once the xpistub dll is loaded. how do i add an installer package to the unix installer? adding a package involves a few steps: add a section named for your <component> to the packages-unix manifest that describes which files from...
...elect the setup types you choose it to be in. finally add a call to generate the xpi at package time by adding a makexpifile("<component>"); call at: <http://lxr.mozilla.org/seamonkey/sou.../makeall.pl#75> you can test it by changing your current working directory to mozilla/xpinstall/packager/unix and running "perl deliver.pl" on the shell prompt. the resulting stub and full installers will be delivered to "mozilla/installer/{stub,sea}". original document information author(s): samir gehani other contributors: curt patrick last updated date: march 12, 2003 copyright information: copyright (c) samir gehani, curt patrick ...

Windows stub installer - Archive of obsolete content
installer? build your entire mozilla tree, which should build the stub installer in the setup directory as well. (if you need to rebuild stub installer, got to /mozilla/xpinstall/wizard/windows/setup and type "nmake /f makefile.win") go to mozilla/xpinstall/wizard/windows/builder on the shell prompt type "perl build.pl". now you will find an installer *and* the xpcom.xpi and other debug xpis delivered to mozilla/dist/win32_d.obj/install. run the stub installer setup.exe from the install directory. if you need to use vc++ to debug the installer: under project | settings | debug set "executable for debug session" to be the path to mozilla/dist/win32_d.obj/install/setup.exe set "working directory" to be the path to mozilla/dist/wind32_d.obj/install press f10 to step into the code how we...
...stalls it when users select the setup types you choose it to be in. finally add <component> to the component list array @gcomponentlist at: <http://lxr.mozilla.org/seamonkey/sou...makeall.pl#125> you can test it by changing your current working directory to mozilla/xpinstall/wizard/windows/builder and running "perl build.pl" on the shell prompt. the resulting stub installer and packages will be delivered to "mozilla/dist/win32obj_d/installer". run setup.exe there to launch the stub installer. original document information author(s): samir gehani other contributors: curt patrick last updated date: march 12, 2003 copyright information: copyright (c) samir gehani, curt patrick ...

Using XPInstall to Install Plugins - Archive of obsolete content
snippet above, the initinstall method is invoked with three parameters: a string for the name of the application a string signifying the plugin identifier associated with the plugin. this value is actually entered in the client version registry upon installation, a mozilla-browser file that stores metadata about the software that has just been installed. this value can be queried via web-page delivered javascript, and is useful for initiating xpinstall downloads via trigger scripts. you can determine the version of the software that has been installed, and determine whether to update it, all via javascript in a web-page. a string representing the four digit version of the software. caveat: certain versions of mozilla-based browsers (such as netscape 6.x) treat the use of the equals character ...
...ent platforms and os's. a single install.js is often capable of running on many different platforms. some installation concerns this section gathers together some of the chief concerns about deploying xpi packages, notably: how ought a plugin download via xpi be initiated? and what about uninstalling plugins? triggering an xpinstall download with a triggerscript a trigger script is web-page delivered piece of javascript that can automatically initiate an xpinstall download. this can be done conditionally, since trigger scripts can also detect what software has already been installed to the user's machine via xpinstall. this feature is useful for web sites because: html pages and javascript already have a way of detecting what plugins are installed. additionally, via the installtrigger objec...

NPP_Write - Archive of obsolete content
void* buf); parameters the function has the following parameters: instance pointer to the current plug-in instance. stream pointer to the current stream. offset offset in bytes of buf from the beginning of the data in the stream. can be used to check stream progress or by range requests from npn_requestread. len length in bytes of buf; number of bytes accepted. buf buffer of data, delivered by the stream, that contains len bytes of data offset bytes from the start of the stream. the buffer is allocated by the browser and is deleted after returning from the function, so the plug-in should make a copy of the data it needs to keep. returns the plug-in should return the number of bytes written (consumed by the instance). if the return value is smaller than the size of the buffer, the ...
..._destroystream. description the browser calls the npp_write function to deliver the data specified in a previous npp_writeready call to the plug-in. a plug-in must consume at least as many bytes as indicated in the npp_writeready call. after a stream is created by a call to npp_newstream, the browser calls npp_write either: if the plug-in requested a normal-mode stream, the data in the stream is delivered to the plug-in instance in a series of calls to npp_writeready and npp_write. if the plug-in requested a seekable stream, the npn_requestread function requests reads of a specified byte range that results in a series of calls to npp_writeready and npp_write. the plug-in can use the offset parameter to track the bytes that are written. this gives you different information depending in the type of...

Index - MDN Web Docs Glossary: Definitions of Web-related terms
omment). 103 dtls (datagram transport layer security) dtls, intro datagram transport layer security (dtls) is a protocol used to secure datagram-based communications. it's based on the stream-focused transport layer security (tls), providing a similar level of security. as a datagram protocol, dtls doesn't guarantee the order of message delivery, or even that messages will be delivered at all. however, dtls gains the benefits of datagram protocols, too; in particular, the lower overhead and reduced latency. 104 dtmf (dual-tone multi-frequency signaling) dtmf, glossary, webrtc dual-tone multi-frequency (dtmf) signaling is a system by which audible tones are used to represent buttons being pressed on a keypad. frequently referred to in the united states as "t...
...ary, security, sql, sql injection, webapp sql injection takes advantage of web apps that fail to validate user input. hackers can maliciously pass sql commands through the web app for execution by a backend database. 394 sri csp, security subresource integrity (sri) is a security feature that enables browsers to verify that files they fetch (for example, from a cdn) are delivered without unexpected manipulation. it works by allowing you to provide a cryptographic hash that a fetched file must match. 395 stun glossary, infrastructure, stun, webmechanics, webrtc stun (session traversal utilities for nat) is an auxiliary protocol for transmitting data around a nat (network address translator). stun returns the ip address, port, and connectivity status of...