Found 502 pages:
| # | Page | Tags and summary |
|---|---|---|
| 1 | Archive of obsolete content | |
| Here at MDN, we try to avoid outright deleting content that might be useful to people targeting legacy platforms, operating systems, and browsers. Perhaps your target audience is people that are using older hardware, for example, and can't upgrade to the latest and greatest browsers. Or for "reasons," your company is required to use very old software and you need to build Web content that runs on that software. Or perhaps you're just curious about the history of an obsolete feature or API, and how it worked. | ||
| 2 | An Interview With Douglas Bowman of Wired News | Web Development, Web Standards |
| One of the Web's oldest news sites, Wired News draws between 20 and 25 million page views every month. On October 11, 2002, Wired launched a brand-new site design that uses validating XHTML for its structure and a small collection of CSS files for its layout. The new design clearly shows what some experts have been saying: that standards-based design can be visually compelling and preserve the interface conventions we've come to expect from Web pages. | ||
| 3 | Archived Mozilla and build documentation | |
| These articles are archived, obsolete documents about Mozilla, Gecko, and the process of building Mozilla projects. | ||
| 4 | ActiveX Control for Hosting Netscape Plug-ins in IE | Add-ons, NeedsClassification, Plugins |
| Microsoft has removed support for Netscape plug-ins from IE 5.5 SP 2 and beyond. If you are a plug-in author, you may find this project saves you a lot of work! | ||
| 5 | Archived SpiderMonkey docs | Archive |
| This section contains old SpiderMonkey documentation. | ||
| 6 | File object | JavaScript, SpiderMonkey |
| Non-Standard Server-Side Object | ||
| 7 | open | |
| Opens the file, specifying file mode and type. | ||
| 8 | Merging TraceMonkey Repo | |
| These are the steps to merge the TraceMonkey repository to mozilla-central. Between resolving conflicts, finding a good time to land, watching the tree, and marking bugs as fixed, it takes around half a day. | ||
| 9 | SpiderMonkey coding conventions | JavaScript, SpiderMonkey |
| The SpiderMonkey project owners enforce coding conventions pretty strictly during code reviews. | ||
| 10 | Automatic Mozilla Configurator | Administration, Configuration management, enterprise |
| No summary! | ||
| 11 | Enabling quicklaunch for all users | Administration, Configuration management, enterprise |
| No summary! | ||
| 12 | How Mozilla finds its configuration files | Administration, Configuration management, enterprise |
| No summary! | ||
| 13 | How Thunderbird and Firefox find their configuration files | Administration, Configuration management, enterprise |
| No summary! | ||
| 14 | Introduction | Administration, Configuration management, enterprise |
| No summary! | ||
| 15 | Kill the XUL.mfl file for good | Administration, Configuration management, enterprise |
| No summary! | ||
| 16 | Locked config settings | Administration, Configuration management, enterprise |
| No summary! | ||
| 17 | Other Mozilla customization pages | Administration, Configuration management, enterprise |
| No summary! | ||
| 18 | Protecting Mozilla's registry.dat file | Administration, Configuration management, enterprise |
| No summary! | ||
| 19 | BlackConnect | Java |
| No summary! | ||
| 20 | Blackwood | Java |
| No summary! | ||
| 21 | Bonsai | Developing Mozilla, Developing_Mozilla:Tools, Tools |
| It is a tool that lets you perform queries on the contents of a CVS archive; you can: get a list of checkins, see what checkins have been made by a given person, or on a given CVS branch, or in a particular time period. It also includes tools for looking at checkin logs (and comments); doing diffs between various versions of a file; and finding out which person is responsible for changing a particular line of code ("cvsblame"). | ||
| 22 | Chromeless | Update |
| [This project may not be active — check Github https://github.com/mozilla/chromeless] | ||
| 23 | Creating a Mozilla Extension | Add-ons, Extensions, Outdated_articles |
| A Mozilla extension is an installable enhancement to the Mozilla browser that provides additional functionality (for example Linky, which adds an item to the context menu for opening multiple links in a document or selection). This tutorial walks you through the process of building a Mozilla extension that adds an icon to Mozilla's status bar showing the current status of the Mozilla source code (i.e. whether or not the latest version of the code is compiling successfully and passing tests). The extension will access Tinderbox, mozilla.org's webtool for tracking source code status, to get the status of the code. | ||
| 24 | Adding the structure | Add-ons, Extensions |
The UI for our extension is an icon in the status bar. To implement this UI, we'll add a statusbarpanel element to the statusbar element in the navigator.xul file. |
||
| 25 | Conclusion | Add-ons, Extensions |
You now have a working Mozilla extension installer! To test it, try installing the extension on a fresh copy of Mozilla by loading the file in your Mozilla browser (this works whether you load it from the web or from your local hard drive via a file:/// URL). Mozilla will automatically detect that the file is an installer and ask you if you want to install the software. Try installing the extension, restarting Mozilla, and see if it works. |
||
| 26 | Enabling the behavior - retrieving tinderbox status | Add-ons, Extensions |
| No summary! | ||
| 27 | Enabling the behavior - updating the status bar panel | Add-ons, Extensions |
| No summary! | ||
| 28 | Enabling the behavior - updating the status periodically | Add-ons, Extensions |
| No summary! | ||
| 29 | Finding the code to modify | Add-ons, Extensions |
| Now that we've found the file to edit, we need to find the specific code within that file. Again, the DOM Inspector makes this easy. The "Document - DOM Nodes" pane on the left-hand side of the Inspector window displays a tree representation of the browser window's XUL file. When you select a node in the tree, a red border flashes for several seconds around the visual representation of that node in the browser window. | ||
| 30 | Finding the file to modify | Add-ons, Extensions |
| No summary! | ||
| 31 | Making a Mozilla installation modifiable | Add-ons, Extensions |
| Mozilla's user interface is made up of XUL (described below), XBL (a topic for another tutorial), JavaScript, CSS, and image files. XUL, XBL, JavaScript, and CSS files are all in text format and can be edited in a standard text editor, while image files are in binary GIF, JPG, or PNG format and must be edited with an image editing program. | ||
| 32 | Making it into a dynamic overlay and packaging it up for distribution | Add-ons, Extensions, Outdated_articles |
Now that we have a static overlay we're in good shape to create a XPI package that installs our extension as a dynamic overlay. XPIs have a complex structure designed to separate UI layers from each other. To make our XPI we'll start out by creating a directory to hold the files we're going to add to the XPI. Then we'll modify URLs in our files so they point to the right place. After that we'll create a contents.rdf file describing the tinderstatus component for the chrome registry and an install.js script to perform the installation. Finally we'll zip the files into an archive. |
||
| 33 | Making it into a static overlay | Add-ons, Extensions |
| Now that we have a working Mozilla extension that shows tinderbox status, we need to make it distributable to other users. The two ways of doing that are to integrate it into the Mozilla codebase (in which case it is no longer an extension but rather part of the default Mozilla distribution) and to package it into an installer that users can run from within Mozilla to add the extension to their Mozilla installation. | ||
| 34 | Prerequisites | Add-ons, Extensions |
| In order to complete this tutorial you need to have and know how to use the following programs on your computer: | ||
| 35 | Specifying the appearance | Add-ons, Extensions |
| Now that we have defined a panel in which to display an icon, we use CSS to specify which icon to display. For this we have to first create four icons, one for each tinderbox state (none, success, test failed, and busted), then create a set of CSS rules that displays the icon corresponding to the current tinderbox state: | ||
| 36 | Tinderbox | Add-ons, Extensions |
| Tinderbox is a web tool for tracking the status of the Mozilla source code. It consists of a set of client machines that continuously build and test Mozilla and report their results back to a server that makes those results available via a web page. The tool enables mozilla.org to be immediately notified of changes to the code that prevent Mozilla from compiling and running (or compromise performance and footprint) so they can get someone to fix the problem or reverse the changes. | ||
| 37 | Dehydra | Dehydra |
| The development focus switched to DXR (where the "D" comes from "Dehydra"), which is based on clang instead of gcc. Try DXR instead, or else try the gcc python plugin: https://fedorahosted.org/gcc-python-plugin/. | ||
| 38 | Dehydra Frequently Asked Questions | Dehydra |
| Initially Dehydra was written as an easy way to look for patterns in Control Flow Graphs (CFGs). Images of those graphs reminded me of the multiheaded Hydra monster. Thus De-hydra can be thought of as a decapitating tool for slaying CFGs. Currently Dehydra does not provide the CFG functionality, this functionality is now provided by Treehydra. | ||
| 39 | Dehydra Function Reference | |
| The following functions may be provided by the analysis script and will be called by Dehydra while compiling. See the Dehydra object reference for details on the available object properties. | ||
| 40 | Dehydra Object Reference | |
| Dehydra represents C++ types and variables as JavaScript objects. The objects are designed to distill that type system to the minimum such that it can be easy to match on. | ||
| 41 | Installing Dehydra | Dehydra |
It is recommended that you use SpiderMonkey revision AURORA_BASE_20110705 when building Dehydra. |
||
| 42 | Using Dehydra | |
| As GCC compiles file, Dehydra calls functions in the user analysis script with information about the code being compiled. For more information, see the function reference and the object reference. | ||
| 43 | Devmo 1.0 Launch Roadmap | MDC Project, MDC Project archives |
| Comments, ideas, questions and other discussion should be added on the Devmo talk:1.0 Launch Roadmap page. Further details on smaller tasks being done are available at User:Dria:TODO page. See also Current Events. | ||
| 44 | Drag and Drop | XUL |
| This section describes how to implement objects that can be dragged around and dropped onto other objects. | ||
| 45 | Drag and Drop Example | XUL |
| An example of implementing drag and drop will be implemented in this section. | ||
| 46 | Drag and Drop JavaScript Wrapper | XUL |
| This section describes how to use the JavaScript wrapper for drag and drop. | ||
| 47 | Drag and drop events | Firefox 3 |
| Firefox 3 adds two new events that allow you to determine when drag operations begin and end. These events are new in the current working draft of the HTML 5 specification. | ||
| 48 | Embedding Mozilla in a Java Application using JavaXPCOM | Embedding Mozilla, JavaXPCOM, Obsolete, XPCOM:Language Bindings |
| XULRunner ships with the JavaXPCOM component, which allows Java code to interact with XPCOM objects. As you will see in this article, working with XPCOM objects in Java is not that much different than doing so in C++. | ||
| 49 | Existing Content | MDC Project |
| This is a list of existing mozilla.org documentation. It needs to be checked, prioritized, and migrated. | ||
| 50 | Extension Frequently Asked Questions | Add-ons, Extensions, Guide, guide |
| This is quick set of answers to the most common issues with extension development. They are currently written with mostly Firefox in mind, but most if not all should easily translate to SeaMonkey, Thunderbird or any of the other applications. For Thunderbird, you may also find the extension HowTo or FAQ pages helpful. | ||
| 51 | Fighting Junk Mail with Netscape 7.1 | User_Documentation |
| Summary: Is your mail account drowning in a flood of spam? Netscape 7.1 includes built-in junk mail filtering that you can train to meet your specific needs. Eric Meyer share his experiences with making the junk mail controls more effective, and looks at other preferences you might want to set to keep your account safe. | ||
| 52 | Firefox Sync | Sync |
| Sync refers to a family of related components and services which provide synchronization of data between Mozilla application instances. These components and services include: | ||
| 53 | Code snippets | |
| This page documents how to perform custom actions with Firefox Sync via JavaScript. | ||
| 54 | JavaScript Client API | Sync |
| This page describes how to use the internal client-side Sync JavaScript API. This API is available in Mozilla-based products that use Sync, such as Firefox desktop. This document is somewhat outdated, and the API isn't well-supported for use from add-ons; tread carefully. | ||
| 55 | Syncing custom preferences | Sync |
| When preferences sync is enabled, Firefox Sync will synchronize preferences between the same application based on a whitelist. That means preferences between Firefox and Fennec, for instance, are never synced. To sync preferences between Firefoxes, Fennecs, Thunderbirds, etc., ensure the prefs are whitelisted. | ||
| 56 | HTTP Class Overview | Necko, Outdated_articles |
| This document provides an overview of the classes used by the Mozilla HTTP implementation. It's meant as a guide to developers wishing to understand or extend the Mozilla HTTP implementation. | ||
| 57 | Hacking wiki | MDC Project archives |
| To be able to hack the MDC wiki software, you'll need a local webserver install, which can run MediaWiki. | ||
| 58 | Help Viewer | Toolkit API, XUL, XULRunner |
| Help Viewer: Allows information to be shown to the user inside Mozilla. | ||
| 59 | Creating a Help Content Pack | |
| Original doc: http://www.mozilla.org/projects/help.../content_packs I hesitate to call it "original", tho, because I've basically rewritten the entire thing so that it's easier and faster to use to create Help content. The previous document had a lot of places where ideas were simply introduced without explanation, and I've tried to go through things a bit more slowly with better descriptions. This is still very much a work in progress, tho, and I need to complete the rest of it soon (where "complete" means "use what's there that's good, build on the stuff that's not as good, and add other useful information as necessary". | ||
| 60 | Hidden prefs | |
| 61 | How to Write and Land Nanojit Patches | Obsolete |
| Adobe and Mozilla share a copy of Nanojit. This means that landing nanojit patches is a bit complicated, but experience has taught us that this is much better than having separate versions of nanojit. | ||
| 62 | Introducing the Audio API extension | Deprecated |
The Audio Data API extension extends the HTML5 specification of the <audio> and <video> media elements by exposing audio metadata and raw audio data. This enables users to visualize audio data, to process this audio data and to create new audio data. |
||
| 63 | JavaScript crypto | Cryptography, Guide, JavaScript, NSS, Non Standard, Security, guide |
Mozilla defines a special JavaScript object to allow web pages access to certain cryptographic-related services. These services are a balance between the functionality web pages need and the requirement to protect users from malicious web sites. Most of these services are available via the DOM window object as window.crypto. |
||
| 64 | CRMF Request object | |
| RFC 4211, the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF), defines a certReqMessage. The object returned by generateCRMFRequest() contains one of those. | ||
| 65 | generateCRMFRequest() | NSS |
| This method will generate a sequence of CRMF requests that has N requests. One request for each key pair that is generated. The first three parameters will be applied to every request. The "escrowAuthorityCert" parameter will only be used for requests that pertain to a key that is being escrowed. After the "escrowAuthorityCert" parameter, the method takes some JavaScript code that is invoked when the CRMF request is ready. Finally, there are 1 or more sets of key generation arguments. Each key generation will be associated with its own request. All the requests will have the same DN. | ||
| 66 | importUserCertificates | NSS |
The importUserCertificates() method is used to import newly issued certificates for the user. The private key for the certificates must already reside in the user's personal private key database. |
||
| 67 | popChallengeResponse | NSS |
The resultString will either be a base-64 encoded POPODecKeyRespContent message, or one of the following error strings: |
||
| 68 | Jetpack | |
| 69 | Basics | |
| Writes some information to the Error Console. You can find the console in the Extra Menu of Firefox. | ||
| 70 | Content | |
| No summary! | ||
| 71 | Page modifications | |
| This documentation is under development. Please see the page modifications API proposal for now. | ||
| 72 | Extenders | |
| No summary! | ||
| 73 | Jetpack Snippets | |
| Bits of code that may come in handy. Feel free to add your own! | ||
| 74 | Libraries | |
Namespace: jetpack.lib |
||
| 75 | ||
Jetpack's Twitter library, jetpack.lib.twitter, is a very simple, lightweight layer on top of Twitter's REST API. In fact it's hardly more than syntactic sugar for doing XMLHttpRequests. |
||
| 76 | Meta | |
| No summary! | ||
| 77 | Enabling | |
| The proposed method for accessing Jetpack features that are still in development and may be added in the future is inspired by python's future module. In Python, you can call | ||
| 78 | Enabling Experimental Jetpack Features | |
| The proposed method for accessing Jetpack features that are still in development and may be added in the future is inspired by python's future module. In Python, you can call | ||
| 79 | First Run | |
| Jetpack lets you specify arbitrary content that will be shown to your users when they install your jetpack. You can also register a callback that will be called after installation. | ||
| 80 | First run | |
| Jetpack lets you specify arbitrary content that will be shown to your users when they install your jetpack. You can also register a callback that will be called after installation. | ||
| 81 | Me | |
The jetpack.me namespace provides mechanisms for introspecting the dynamic state of your jetpack. The namespace currently lives in the future and must be imported before it is used: |
||
| 82 | Settings | |
| The jetpack.storage.settings namespace allows jetpacks to specify user-configurable settings. Jetpack will automatically generate a user interface based on the specification. The settings persist across browser sessions and are stored using the Jetpack [simple storage API][]. Settings are private to each jetpack and are not accessible by other jetpacks. | ||
| 83 | Multimedia | |
| No summary! | ||
| 84 | Storage | |
| No summary! | ||
| 85 | File access | |
| Click on the paper-clip icon below for a demonstration of the file upload dialog. | ||
| 86 | Settings | |
The jetpack.storage.settings namespace allows jetpacks to specify user-configurable settings. Jetpack will automatically generate a user interface based on the specification. The settings persist across browser sessions and are stored using the Jetpack simple storage API. Settings are private to each jetpack and are not accessible by other jetpacks. |
||
| 87 | Simple Storage | |
The jetpack.storage.simple namespace provides an easy way to persist data across browser restarts. It's a simple key-based persistent object data store. |
||
| 88 | System | |
| No summary! | ||
| 89 | Clipboard | |
| Jetpack's clipboard support API provides a standardized way for features to access the clipboard. Features can get and set the clipboard in various flavors of data type. | ||
| 90 | Clipboard | |
| Jetpack's clipboard support API provides a standardized way for features to access the clipboard. Features can get and set the clipboard in various flavors of data type. | ||
| 91 | Clipboard Test | |
| <style></style> | ||
| 92 | Clipboard Test | |
| Jetpack's clipboard support API provides a standardized way for features to access the clipboard. Features can get and set the clipboard in various flavors of data type. | ||
| 93 | System information | |
| This documentation is under development. Please see the system information API proposal for now. | ||
| 94 | UI | |
| No summary! | ||
| 95 | Menu | |
| Jetpack's menu API allows features to access and modify the browser's built-in menus. Features can also create new menus and attach them almost anywhere, chrome or content, as popup menus or context menus. | ||
| 96 | Notifications | |
| The Notification Box appears at the bottom right corner of the browser and displays important information to the user. | ||
| 97 | Panel | |
| Please refer to the Panels JEP. | ||
| 98 | Selection | |
| Jetpack's selection API provides a method for detecting the selections made by the user. Features can get, set, and listen for selection events in HTML or plain text. | ||
| 99 | Selection | |
| Jetpack's selection API provides a method for detecting the selections made by the user. Features can get, set, and listen for selection events in HTML or plain text. | ||
| 100 | Tabs | |
| In this class you can find information about the tabs in your Firefox window. | ||
| 101 | Wiki Test Page | |
| No summary! | ||
| 102 | jetpack.tab | |
| No summary! | ||
| 103 | slideBar | |
| slideBar is a reinvention of the old sidebar features of browsers. They allow quick access to a wide range of both temporary and permanent information at the side of your browser window. When a slideBar feature is selected its contents will be revealed from behind the current webpage. | ||
| 104 | slideBar | |
To implement a new slideBar within your jetpack code, use the method jetpack.slideBar.append(options) |
||
| 105 | Users | |
| No summary! | ||
| 106 | aza | |
| No summary! | ||
| 107 | Dropbox | |
| No summary! | ||
| 108 | docs | |
| No summary! | ||
| 109 | Meta | |
| No summary! | ||
| 110 | Enabling Experimental Jetpack Features | |
| The proposed method for accessing Jetpack features that are still in development and may be added in the future is inspired by python's future module. In Python, you can call | ||
| 111 | Storage | |
| No summary! | ||
| 112 | Simple Storage | |
The jetpack.storage.simple namespace provides an easy way to persist data across browser restarts. It's a simple key-based persistent object data store. |
||
| 113 | System | |
| No summary! | ||
| 114 | Clipboard | |
| Jetpack's clipboard support API provides a standardized way for features to access the clipboard. Features can get and set the clipboard in various flavors of data type. | ||
| 115 | UI | |
| No summary! | ||
| 116 | Selection | |
| Jetpack's selection API provides a method for detecting the selections made by the user. Features can get, set, and listen for selection events in HTML or plain text. | ||
| 117 | jspage | |
| No summary! | ||
| 118 | statusBar | |
| No summary! | ||
| 119 | statusBar | Class |
| The Class statusBar contains functions to add and control the Statusbar of the Browser. You can find the complete Sourcecode in the status-bar-panel.js file in your Jetpack Repository. | ||
| 120 | Litmus tests | |
| Litmus tests are (non-automated) tests that are documented in the litmus database. See http://litmus.mozilla.org. | ||
| 121 | Mercurial | Developing Mozilla, Mercurial |
| Please refer to Mercurial For Mozillians at ReadTheDocs for current best-practices around Mercurial, including many helpful extra tools and guidelines that make using Mercurial fast and easy. | ||
| 122 | Mercurial Queues | Build documentation, Developing Mozilla, Mercurial |
| Mercurial Queues, or MQ, is a Mercurial extension that lets you keep work in progress as mutable patches, instead of as immutable changesets. | ||
| 123 | Mercurial basics | Developing Mozilla, Mercurial |
| I am about to tell you some stuff about Mercurial that will save you a lot of frustration. This page is cynical and survival-oriented. But I still claim Mercurial is a lot better than CVS. —jorendorff 16:06, 12 May 2008 (PDT) | ||
| 124 | Mercurial/Desired Features | Mercurial |
| Provide named anchors for various elements so that users may post links to them in bug reports, etc. | ||
| 125 | Reverting Changesets With File Moves/Renames | Mercurial |
| Normally backing out a changeset in Mercurial is as simple as: | ||
| 126 | Microsummary topics | Microsummaries |
To programmatically install a microsummary generator -- for example, in an extension that helps users create custom generators for their favorite sites -- obtain a reference to the nsIMicrosummaryService interface implemented by the nsIMicrosummaryService component, then call its installGenerator() method, passing it an XML document containing the generator. |
||
| 127 | Microsummary XML grammar reference | Microsummaries |
| A microsummary generator is an XML document that describes how to pull specific information from a web page to be presented in summary form as a bookmark whose title changes based on the content of the page it targets. | ||
| 128 | New Skin Notes | MDC Project, MDC Project archives |
| Devmo has a new skin that is ready for testing. If you go to your user preferences, you can change the skin to "Devmo". This is currently just a preview, but we would appreciate help with testing. | ||
| 129 | Plugin Architecture | Add-ons, Developing Mozilla, NeedsTechnicalReview, NeedsUpdate, Plugins |
| This page contains some notes on how plugins work internally in Gecko. It is mainly of interest to Gecko developers. | ||
| 130 | Priority Content | MDC Project |
| Update: I've removed documents from this list that have been migrated into the wiki. The list of completed documents is available through the DevEdge page. | ||
| 131 | Prism | prism |
| Prism is a simple XULRunner-based browser that hosts web applications without the normal web browser user interface. Prism is based on a concept called Site-Specific Browsers (SSB). An SSB is designed to work exclusively with a single web application. It doesn’t have the menus, toolbars and other accoutrements of a traditional web browser. An SSB also offers tighter integration with the operating system and desktop than a typical web application running through a web browser. Applications running in an SSB are therefore able to benefit from many of the advantages of the desktop and of the web at the same time. | ||
| 132 | BlogPosts | prism |
| Just Browsing: Mozilla Prism Update ThansCorner: Mozilla Prism - Webrunner with Pazzaz Mozilla Prism - A Revolution in Web Apps ThansCorner: Mozilla WebRunner 0.7 Site Specific Browsers WebRunner Using WebRunner WebRunner + Gears = Offline Desktop Reader WebRunner 0.5 WebRunner 0.5 - Mac Support WebRunner 0.5 - Linux Install WebRunner, Google Reader, and Google Notebook Distraction Free GTD - 32+ web app files for online todo lists Mozilla WebRunner: a one-window, tabless browser with no URL bar WebRunner becomes Prism - A Mozilla Labs Project Mozilla Labs: Prism Alex Faaborg: Prism Mozilla Prism: Bringing Web Apps to the Desktop Everyone should use Site Specific Browsers Mozilla Prism Portable (Spanish) Prism, l'avenir des applications Web selon Mozilla (French) Mozilla Prism : bundle custom Google Reader + Talk (French) Just Browsing: Site-Specific Browsers |
||
| 133 | Build | |
| Building Prism is similar to building McCoy, but there are some differences which is why a separate build documentation article. To build prism, you must first build the xulrunner tree, and then build prism. | ||
| 134 | BundleLibrary | prism |
| No summary! | ||
| 135 | Bundles | prism |
| In addition to passing simple command line parameters, Prism can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to: | ||
| 136 | Configuration | prism |
| A webapp profile is a simple, INI-style text file that specifies some parameters about a webapp. The profile can be used to launch the webapp in Prism. The parameters also control some of the features of the Prism host window. Here is the list of parameters: | ||
| 137 | Extensions | |
| Prism has support for extensions. Extensions are built using the same methods as any Mozilla-based extension. Since Prism is a totally separate host application, there are some Prism-specific issues that you need to handle when creating your extension. Most notably, the Prism application ID and the differences in the user interface (UI). Extensions typically overlay the host application's UI to add toolbar buttons, menus and other features. One of Prism's features is an extreme lack of UI elements, which means that trying to use the same overlays in Firefox and Prism is really not possible. | ||
| 138 | FAQ | prism |
| Prism is an application that integrates web applications into the desktop environment. It lets users start web applications from their desktop, start menu, and dock, and it opens those applications in their own window separate from a web browser and without the browser interface (back and forward buttons, location bar, etc.). | ||
| 139 | HostWindow | prism |
| Prism hosts web applications in a simple, minimal window. The window does have some UI components (as shown in the screenshot below). Prism can be configured to show or hide several of the UI components. | ||
| 140 | Installer | prism |
| The installer should configure the OS to associate *.webapp files with Prism. This means that when you double-click or launch a *.webapp file, Prism is launched and automatically opens the web application. | ||
| 141 | Scripting | prism |
| Prism allows for some client-side web application customization. The web application bundle is allowed to hold a JavaScript file named webapp.js (called the webapp script). This file will be loaded into the Prism chrome window very much like a Firefox extension is loaded into the browser chrome window. It can contain the following functions: | ||
| 142 | Styling | prism |
| Prism allows for some client-side web application styling. The web application bundle is allowed to hold a CSS file named webapp.css (called the webapp style). This file will be loaded into the web application content stylesheet and can override the web application's native styles. | ||
| 143 | Proxy UI | |
| (Recently Added - some support for reading OS and account settings.) | ||
| 144 | Remote XUL | XUL |
| How to use XUL delivered from a webserver, not as part of chrome. | ||
| 145 | SXSW 2007 presentations | Presentations |
| Presentations about the Mozilla project given at the SXSW 2007 event in Austin, Texas. | ||
| 146 | Space Manager Detailed Design | Gecko |
| The Space Manager and related classes and structures are an important of the Gecko Layout system, specifically Block Layout. See the High Level Design document for an overview of the Space Manager, and as an introduction to the classes, structures and algorithms container in this, the Detailed Design Document. | ||
| 147 | Space Manager High Level Design | Gecko |
| The Space Manager and associated classes and structures are used by Block and Line layout to manage rectangular regions that are occupied and available, for correct handling of floated elements and the elements that flow around them. When elements are floated to the left or right in a layout, they take up space and influence where other elements can be placed. The Space Manager is responsible for keeping track of where space is taken up and where it is available. This information is used by block layout to correctly compute where other floated elements should be placed, and how much space is available to normal in-flow elements that flow around the floated bits. | ||
| 148 | Stress testing | |
| Consume.exe from the Windows Server 2003 Resource Kit Tools can consume various resources: physical memory, CPU time, page file, disk space and even the kernel pool. Although for Win2003, it should install into WinXP fine (Win2000 compatibility is unknown). The only downside is you can't specify how much of the resource to use, only which one to consume. Also be warned: always remember the -time option, or you may be hitting that physical reset button sooner than you would have liked! | ||
| 149 | Tamarin | JavaScript, Landing, Tamarin |
| No summary! | ||
| 150 | ABCasm | |
| ABCasm - an ABC assembler | ||
| 151 | Tamarin Acceptance Testing | |
| In order to ensure that changes to the Tamarin code base are high quality before submitting, all developers are required to complete the following steps. | ||
| 152 | Abc Assembler Tests | |
| It is possible to write tests using the abc assembler. The assembler code can be found in /utils/abcasm. Tests can be found in /test/acceptance/abcasm and end with the .abs extension. The tests are run using the same runtests.py script that is used for the actionscript tests. | ||
| 153 | Actionscript Acceptance Tests | |
| The majority of the acceptance tests are written in actionscript and located in test/acceptance. | ||
| 154 | Tamarin Acceptance Test Template | |
| This is the test template for Tamarin acceptance tests (placed in test/acceptance/feature_name): | ||
| 155 | Actionscript Performance Tests | |
| Performance tests for tamarin are located in the test/performance directory. Similar to the acceptance tests set the environment variables AVM, ASC, BUILTINABC. The runtests.py test harness works by parsing the abc stdout for lines like: 'metric time 566'. The testconfig.txt file defines groups of tests to run (e.g. sunspider, scimark, language). By default the time for each test is output. Use the --memory flag to capture the maximum private bytes memory (high water mark) for a test. By default each test is run a single time. To run each test multiple times use the --iterations flag. When the number of iterations is greater than 2 all times are displayed in [], faster time is displayed in the output column, and the 95% confidence interval is calculated. The 95% confidence interval is the calculated percentage of the mean value to fall within 95% of the measured results. For example if the mean is 100 and the 95% confidence interval is 2%, 95% of the expected values should fall between 98 and 102. To compare two vms against each other export AVM2=<path vm="" 2nd="" to=""> or use --avm2=<path vm="" 2nd="" to="">. The percentage difference is calculated between the two vms. See the --help usage for more details about performance tests.</path></path> | ||
| 156 | Cmdline tests | |
| The cmdline testsuite is located in test/cmdline. The testsuite allows more flexibility by coding scripts in python allowing any executable to run, sending commands to stdin, and asserting output using regular expressions. See test/cmdline/README document for more information. Two use cases for the cmdline testsuite: | ||
| 157 | Running Tamarin acceptance tests | |
| The Tamarin acceptance tests can be used to verify your installation and or local changes that you have made to the source. To run acceptance tests on the android shell see the "Testing the Android Shell" heading below. Running the Tamarin test suite requires the following steps: | ||
| 158 | Running Tamarin performance tests | |
| The tamarin performance tests can be used to measure performance changes made to tamarin. To run performance tests on the android shell see 'Testing the Android Shell' below. Running the performance tests requires the following steps: | ||
| 159 | Tamarin Build System Documentation | |
| No summary! | ||
| 160 | Tamarin Releases | |
| This page tracks Tamarin source code releases, past, present and future. | ||
| 161 | Tamarin-central rev 703:2cee46be9ce0 | |
| <font color="#000000">Tamarin-Central rev 703:2cee46be9ce0 was declared stable on 12/02/08. The announcement sent to tamarin-devel can be read here.</font> | ||
| 162 | Tamarin Roadmap | |
| The Tamarin roadmap is intended to provide visibility into planned features and release dates. The roadmap is a living document representing current best thinking and is subject to change. Comments or questions are welcome and encouraged via the tamarin-devel mailing list. | ||
| 163 | Tamarin build documentation | Build documentation, Developing Mozilla, Tamarin |
| The following instructions are for obtaining and building the Tamarin Central source code. For instructions on Tamarin Tracing, please see Tamarin Tracing Build Documentation. | ||
| 164 | Tamarin mercurial commit hook | |
| It is highly recommended that all developers enable the mercurial commit hook for tamarin. The hook is located in the tamarin-redux repository in the file utils/hooks/tamarin-commit-hook.py | ||
| 165 | Treehydra | Treehydra |
| Try the gcc python plugin instead: https://fedorahosted.org/gcc-python-plugin/. | ||
| 166 | Treehydra Build Instructions | Dehydra |
| Follow Dehydra build instructions. This automatically builds Treehydra for you. | ||
| 167 | Treehydra Manual | |
| Treehydra is meant to be used for analyses that need more detail than Dehydra's flattened ASTs. Instead of representing code in "easy" form like Dehydra, Treehydra relies on GIMPLE, the GCC Internals "middle-end" intermediate representation. Treehydra simply reflects the GCC Internals structures into JavaScript. | ||
| 168 | Using Monotone With Mozilla CVS | Build documentation, Developing Mozilla |
| No summary! | ||
| 169 | Venkman | Extensions, Extensions:Tools, JavaScript, JavaScript:Tools, Tools, Venkman, Web Development, Web Development:Tools |
| Venkman is the code name for Mozilla's JavaScript Debugger. It aims to provide a powerful JavaScript debugging environment for Mozilla based browsers namely Firefox, Netscape 7.x/9.x and SeaMonkey. Note that it is not included in the Gecko-based browsers such as K-Meleon, Galeon and Netscape 8.x. Venkman has been provided as part of the Mozilla install distribution since October 2001, as well as an extension package in XPI format. | ||
| 170 | Using Breakpoints in Venkman | Tools, Venkman |
| This article continues a series of articles on Venkman that began with Venkman Introduction. | ||
| 171 | Venkman Internals | Developing Mozilla, Tools, Venkman |
| Start with Venkman Information. | ||
| 172 | Venkman Introduction | Tools, Venkman |
| A powerful new tool is available for web developers for use in many Mozilla-based products, including Firefox, Mozilla Suite and Netscape 7.x. The JavaScript debugger, also called Venkman, has been a part of the Mozilla browser and the community of web and script developers there for some time. This article provides an overview and some practical examples of using the JavaScript debugger in web applications and web page scripting. This introduction is the first in a series of articles on Venkman and JavaScript debugging. Even if you are already using Venkman, the features, procedures, and tips described here will make you a more confident web developer and debugger. | ||
| 173 | Video presentations | Presentations |
| Mozilla is actively working to produce video presentations that can help you learn how the Mozilla codebase works and how to take advantage of its technology in your own applications and extensions. This article is a jumping-off point to help you find those presentations. | ||
| 174 | XPInstall | XPInstall, XPInstall_API_reference |
| No summary! | ||
| 175 | Creating XPI Installer Modules | XPInstall |
Mozilla has introduced major changes to the way that themes and all the other parts of the UI are packaged. This new packaging scheme is called XPI (pronounced "zippy"), and interacts with XPInstall. A XPI file typically contains the resources to be installed (in this case the barley.jar we want to have installed in the Mozilla/bin/chrome/ directory) and an install script that guides the installation process. |
||
| 176 | Install Wizards (aka: Stub Installers) | Outdated_articles, XPInstall |
| No summary! | ||
| 177 | Mac stub installer | XPInstall |
| No summary! | ||
| 178 | Unix stub installer | XPInstall |
| No summary! | ||
| 179 | Windows stub installer | XPInstall |
| No summary! | ||
| 180 | Learn XPI Installer Scripting by Example | XPInstall, XPInstall_API_reference |
| No summary! | ||
| 181 | Installer Script | |
| No summary! | ||
| 182 | Using XPInstall to Install Plugins | Add-ons, Plugins, XPInstall, XPInstall_API_reference |
| No summary! | ||
| 183 | Install script template | Add-ons, Plugins, XPInstall |
| No summary! | ||
| 184 | XPInstall API reference | XPInstall, XPInstall_API_reference |
| See complete list | ||
| 185 | Examples | |
| Trigger Scripts and Install Scripts describes typical kinds of script that use the XPInstall API. | ||
| 186 | File.macAlias | |
| In this example, a mac alias is created for software (AppleCD Audio Player) that is installed locally. | ||
| 187 | File.windowsShortcut | |
| In this example, the windowsShortcut method is used to add a shortcut in the Program directory ("Program" is a keyword for the directory in which the program itself is installed, for example, C:\Program Files\Netscape\Netscape 6\" on Windows) to Windows software (misc.exe) that is installed in the "Windows" directory. | ||
| 188 | Install.addDirectory | |
| The Install object's addDirectory method queues an entire directory for installation once performInstall is called. | ||
| 189 | Install.addFile | |
| The Install object's addFile method is the standard way to queue files for installation. | ||
| 190 | InstallTrigger.installChrome | |
| Trigger scripts are typically invoked by JavaScript event handlers on hyperlinks. When a user clicks the link "Install the New Blue theme" in the example below, XPInstall downloads, registers, and installs the theme contained in newblue.xpi to the user's profile directory. | ||
| 191 | InstallTrigger.startSoftwareUpdate | |
| This is a very simple example of the InstallTrigger object's principal method, startSoftwareUpdate, which takes a string representing the path to the XPI and installs that XPI on the local machine. | ||
| 192 | Trigger Scripts and Install Scripts | |
| Trigger scripts are simple installations that can be initiated from event handlers and other JavaScript code on a web page. | ||
| 193 | Windows Install | |
| This example shows the installation of a XPI in which user profile information is contained. | ||
| 194 | File Object | |
| Use the File object to manipulate local files and directories during the installation process. | ||
| 195 | Methods | |
| No summary! | ||
| 196 | Install Object | XPInstall_API_reference |
Use the Install object to manage the downloading and installation of software with the XPI Installation Manager. |
||
| 197 | Methods | |
| No summary! | ||
| 198 | Properties | |
| No summary! | ||
| 199 | InstallVersion Object | |
You use InstallVersion objects to contain version information for software. |
||
| 200 | Methods | |
| No summary! | ||
| 201 | Properties | |
| No summary! | ||
| 202 | Return Codes | |
| The methods described in this chapter can return any of the following return codes. In Mozilla/SeaMonkey, these constants are defined as part of the xpinstall object (formerly the SoftwareUpdate object in Netscape Communicator 4.5). | ||
| 203 | WinProfile Object | |
(Windows only) Windows developers use this object to manipulate the content of a Windows .ini file. |
||
| 204 | Methods | |
| No summary! | ||
| 205 | WinReg Object | |
| (Windows only) | ||
| 206 | Methods | |
The WinRegValue constructor creates a WinRegValue object. |
||
| 207 | WinRegValue | |
| (Windows only) | ||
| 208 | XTech 2005 Presentations | Presentations |
| No summary! | ||
| 209 | Directions of the Mozilla RDF engine | Presentations, RDF |
| This presentation showed new developments in the Mozilla RDF engine. These include plans to expose the RDF API to public web content, as well as performance and correctness improvements. | ||
| 210 | Extending Gecko with XBL and XTF | Presentations, XBL, XTF |
| This session explored ways to extend Mozilla/Firefox to handle new XML tags and namespaces via drop-in extensions to the layout engine. | ||
| 211 | Mozilla E4X | E4X, JavaScript, Presentations |
| "ECMAScript for XML" (ECMA-357), a new standard for writing and processing XML directly in JavaScript (ECMA-262, ISO-16262). E4X marries XML and JavaScript syntax, and extends JavaScript to include namespaces, qualified names, and XML elements and lists. E4X also adds new JavaScript operators for filtering XML lists, and for enumerating XML children and descendants. Another E4X feature: the ability to bind a W3C DOM document to a new XML object, reflecting the DOM in E4X terms so that updates to either the DOM or the E4X object hierarchy show up in the other. | ||
| 212 | Rich Web | |
| No summary! | ||
| 213 | SVG And Canvas In Mozilla | Presentations, SVG |
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. |
||
| 214 | XUL - Mozilla's XML User Interface Language | Presentations, XUL |
| Ben Goodger, lead engineer for Mozilla Firefox talked about XUL, Mozilla's XML User Interface toolkit. | ||
| 215 | XTech 2006 Presentations | Presentations |
| No summary! | ||
| 216 | Archived open Web documentation | Archived, Web |
| The documentation listed below is archived, obsolete material about open Web topics. | ||
| 217 | E4X | E4X, Guide, JXON, JavaScript, Obsolete, XML, guide |
| ECMAScript for XML (E4X) is a programming language extension that adds native XML support to JavaScript. It does this by providing access to the XML document in a form that feels natural for ECMAScript programmers. The goal is to provide an alternative, simpler syntax for accessing XML documents than via DOM interfaces. A valid alternative to E4X is a non-native JXON algorithm. | ||
| 218 | E4X for templating | E4X |
| E4X can be used for creating templates for dynamic content. | ||
| 219 | Processing XML with E4X | E4X, Guide, JavaScript, Obsolete, XML, guide |
| First introduced in JavaScript 1.6, E4X introduces a native XML object to the JavaScript language, and adds syntax for embedding literal XML documents in JavaScript code. | ||
| 220 | E4X Tutorial | E4X, JavaScript, XML |
| This tutorial walks you through the basic syntax of E4X (EcmaScript for XML). With E4X, programmers can manipulate an XML document with a syntax more familiar to JavaScript programming. | ||
| 221 | Accessing XML children | |
| Normal JavaScript Objects use the . operator or [] notation to set properties. | ||
| 222 | Descendants and Filters | |
In many cases, the node that you're interested in is not the direct child of the top XML element. Instead, it may be nested several levels down. You can access nodes at any depth using the .. operator, or by using the descendants property. For instance |
||
| 223 | Introduction | E4X, JavaScript, XML |
| With E4X enabled, basic XML elements are valid syntax for variables. For instance | ||
| 224 | Namespaces | |
| Oftentimes, XML documents will contain elements from a variety of namespaces. You can declare the default namespace for your E4X objects by placing the statement: | ||
| 225 | The global XML object | |
E4X-capable JavaScript engines put a new property on the global object. The XML object has several properties that allow you to customize parsing and serialization of E4X. XML elements will remember the settings of the XML object from the time of their creation. |
||
| 226 | LiveConnect | Java, LiveConnect |
| (Please update or remove as needed.) | ||
| 227 | LiveConnect Overview | Advanced, Java, JavaScript, LiveConnect |
| This chapter describes using LiveConnect technology to let Java and JavaScript code communicate with each other. The chapter assumes you are familiar with Java programming. | ||
| 228 | LiveConnect Reference | |
| This section documents the Java classes used for LiveConnect, along with their constructors and methods. | ||
| 229 | JSException | |
| No summary! | ||
| 230 | JSObject | |
The public final class netscape.javascript.JSObject extends Object. |
||
| 231 | MSX Emulator (jsMSX) | Canvas_examples, Examples, HTML:Canvas |
| No summary! | ||
| 232 | Old Proxy API | API, Guide, JavaScript, Non Standard, SpiderMonkey |
| Proxies are objects for which the programmer has to define the semantics in JavaScript. The default object semantics are implemented in the JavaScript engine, often written in lower-level languages like C++. Proxies let the programmer define most of the behavior of an object in JavaScript. They are said to provide a meta-programming API. | ||
| 233 | Scope Cheatsheet | JavaScript, hoisting, scope, variables |
JavaScript with Mozilla extensions has both function-scoped vars and block-scoped lets. Along with hoisting and dynamic behavior, scope in JavaScript is sometimes surprising. |
||
| 234 | Server-Side JavaScript | Guide, JavaScript, backend, serverside javascript, tracemonkey |
| Here's a radical idea: Use one language to write entire Web apps -- the same language which billions of web pages already use, every day. | ||
| 235 | Back to the Server: Server-Side JavaScript On The Rise | Guide, JavaScript, guide |
| by Davey Waterson, JavaScript Architect, Aptana | ||
| 236 | Sharp variables in JavaScript | JavaScript |
| A sharp variable is a syntax in object initializers that allows serialization of objects that have cyclic references or multiple references to the same object. | ||
| 237 | Standards-Compliant Authoring Tools | HTML, HTML:Tools, Tools, XHTML, XHTML:Tools |
| Creating cross-browser code upfront will save you lots of time quality testing your web content. The following authoring tools adhere to the W3 standards. If you're using older versions of tools that rely on old browser bugs or generate browser-specific code, it may be time to upgrade: | ||
| 238 | XForms | XForms |
| No summary! | ||
| 239 | Building Mozilla XForms | XForms |
| Things to know first: | ||
| 240 | Community | XForms |
| No summary! | ||
| 241 | Developing Mozilla XForms | |
Always start with a debug build of the xforms and the schema-validation extensions. See Building Mozilla XForms for a .mozconfig for debug builds. You should create a new, clean profile for debugging. Then start Firefox out of the build directory: |
||
| 242 | Implementation Status | |
| The extension has some limitations and custom extension to the XForms 1.1 specification. These can be found on the Mozilla XForms Specials page. | ||
| 243 | Mozilla XForms Specials | XForms |
| No summary! | ||
| 244 | Mozilla XForms User Interface | XForms |
| This article is a quick reference of the XForms user interface elements. Mainly this is aimed to document how XForms elements will be presented in Mozilla since the XForms specifications give only a hint of how controls might be rendered. | ||
| 245 | XForms Alert Element | XForms |
| No summary! | ||
| 246 | XForms Group Element | XForms |
The group element is used as a container for defining a hierarchy of form controls. Groups can be nested to create complex hierarchies. |
||
| 247 | XForms Help Element | XForms |
| No summary! | ||
| 248 | XForms Hint Element | XForms |
| No summary! | ||
| 249 | XForms Input Element | XForms |
| No summary! | ||
| 250 | XForms Label Element | XForms |
| No summary! | ||
| 251 | XForms Message Element | XForms |
| No summary! | ||
| 252 | XForms Output Element | XForms |
| No summary! | ||
| 253 | XForms Range Element | XForms |
| No summary! | ||
| 254 | XForms Repeat Element | XForms |
| No summary! | ||
| 255 | XForms Secret Element | XForms |
| No summary! | ||
| 256 | XForms Select Element | XForms |
| No summary! | ||
| 257 | XForms Select1 Element | XForms |
| No summary! | ||
| 258 | XForms Submit Element | XForms |
This form control initiates a submission. The result of which is all or part of an instance document being sent to a target destination, which could be local or remote (see the spec). Upon receiving a DOMActivate event, this form control dispatches a xforms-submit event to the submission element (see the spec) specified in its submission attibute. |
||
| 259 | XForms Switch Module | XForms |
XForms Switch Module define a switch construct that allows the creation of user interfaces where the user interface can be varied based on user actions and events. The module defines for this switch, case and toggle elements. |
||
| 260 | XForms Textarea Element | XForms |
| No summary! | ||
| 261 | XForms Trigger Element | XForms |
| Allows the user to initiate actions (see the spec). Actions are described by the XForms Action Module (see the spec). | ||
| 262 | XForms Upload Element | XForms |
| No summary! | ||
| 263 | Other Resources | XForms |
| No summary! | ||
| 264 | Requests For Enhancement | XForms |
| No summary! | ||
| 265 | RFE to the Custom Controls | XForms |
| No summary! | ||
| 266 | RFE to the Custom Controls Interfaces | XForms |
| No summary! | ||
| 267 | RFE to the XForms API | XForms |
| No summary! | ||
| 268 | Troubleshooting XForms Forms | XForms |
| No summary! | ||
| 269 | Using XForms and PHP | XForms |
| No summary! | ||
| 270 | XForms API Reference | XForms |
| The XForms interfaces has the following naming convention: | ||
| 271 | XForms Config Variables | XForms |
| No summary! | ||
| 272 | XForms Custom Controls | XForms |
You are in the right place if you would like to create your own custom renderings of the XForms controls like input, output, trigger, etc. We will also show you how to create custom controls that work with the XForms model and are automatically updated just like XForms controls. The purpose of this article is to give you enough background information so that you'll be able to get a good start. To really grasp the following information, a good understanding of XForms, XBL, JavaScript and CSS is needed. XPCOM knowledge will certainly not hurt. But even if you are only comfortable with a couple of these technologies, we hope that the possibilities outlined below will inspire you to learn more where you need to. |
||
| 273 | XForms Custom Controls Examples | XForms |
| No summary! | ||
| 274 | XForms Styling | XForms |
| No summary! | ||
| 275 | Index | |
| Found 502 pages: | ||
| 276 | MDN "meta-documentation" archive | Archive, MDN |
| Here you'll find archived "meta-documentation"; that is, documentation about how to write documentation on MDN. The articles here are obsolete and should no longer be referenced; we are retaining them here for reference while we migrate some content to new places, but very little of this is useful. | ||
| 277 | Author List with Addresses | MDC Project, MDC Project archives |
| No summary! | ||
| 278 | Blog posts to integrate into documentation | MDC Project |
| Often, Mozilla developers and community members write blog posts. And often, those blog posts are really, really awesome. And, often, those blog posts include information that really ought to be included on MDN. Sometimes, it's the entire blog post that could be adapted into a tutorial on MDN (but please check with the author first, unless they're known to have given blanket permission!), and other times, there are just details about changes to Firefox or web technologies that we need to be sure are reflected in the right places in the docs. | ||
| 279 | Canvas documentation improvements | Doc Plan, Documentation, MDC Project, MDN |
| The goal of this project is to thoroughly revamp our existing canvas and 2D rendering context documentation, including both the reference material and tutorials/guides, by finding, organizing, cleaning up, and updating existing documentation, adding new documentation to cover features not yet documented, and adding new and useful examples that use the live sample system. | ||
| 280 | Current events | |
| No summary! | ||
| 281 | Custom CSS classes for MDN | MDC_Project, MDN, Reference, Référence |
| The following are the custom CSS classes that we have defined for the Devmo wiki. If, for whatever reason, you need a custom class defined in the CSS for this wiki, feel free to contact the documentation team lead. | ||
| 282 | CSS Quick Learn | CSS |
| helps to quickly learn CSS for the development of webpages and become a better web designer. | ||
| 283 | Design Document | |
| No summary! | ||
| 284 | Contribution and Maintenance | |
| No summary! | ||
| 285 | Footer | |
| No summary! | ||
| 286 | MDC Community Index Page | |
| No summary! | ||
| 287 | MDC Content Page | |
| No summary! | ||
| 288 | MDC Content Page (for printing) | |
| No summary! | ||
| 289 | MDC Home Page | |
| No summary! | ||
| 290 | MDC News Index Page | |
| No summary! | ||
| 291 | MDC Reference Index Page | |
| No summary! | ||
| 292 | MDC Reference Library Page | |
| No summary! | ||
| 293 | MDC Topic Page | |
| No summary! | ||
| 294 | MDC WebWatch Index Page | |
| No summary! | ||
| 295 | Navigation Bar | |
| No summary! | ||
| 296 | Page Tools | |
| No summary! | ||
| 297 | Returning User | |
| No summary! | ||
| 298 | Search Box | |
| No summary! | ||
| 299 | Searching for Information | |
| No summary! | ||
| 300 | Side Bar | |
| The side bar provides local navigation options to help readers find related resources. Most pages use the standard side bar, but some pages (see the types of pages) will customize the content. In all cases, the look & feel of the sidebar should be the same. | ||
| 301 | DevEdge | |
| This is a temporary Index of the content that has been migrated from DevEdge to this wiki. The original list and mirror are linked below. | ||
| 302 | Developer documentation process | Documentation, MDC Project |
| In order to improve the quality of our documentation, and our ability to coordinate among the various members of the Mozilla documentation community, we have a process by which documentation is maintained. This article describes how this works and offers useful links to help you ensure that the work you do is as helpful and useful as possible to the community of Web and Mozilla developers. | ||
| 303 | Disambiguation | |
| Disambiguation in the MDC wiki is the process of resolving ambiguity, referring to the conflicts that occur when articles about two or more different topics have the same "natural" title. | ||
| 304 | Documentation Wishlist | |
| Is there a specific article or piece of documentation we're missing that you really wish we had? Add it to the list below. Unless you're sure there is no documentation on the topic you're interested in, please ask in the relevant newsgroup and/or on the MDC mailing list first. Also, please make your request easy to understand; add a link to a longer description of the request if needed. | ||
| 305 | Documentation planning and tracking | Documentation, MDC Project, MDN |
| We are in the process of trying to use scrumbugs to track documentation from the point at which the bug is filed through prioritization, assignment to a writer, and eventual completion. This page will cover some details of how we use it. | ||
| 306 | Editing MDN pages | |
| This page describes some common tasks when editing MDN pages. | ||
| 307 | Examples | MDC Project |
| No summary! | ||
| 308 | Alternate License Block | MDC Project |
| No summary! | ||
| 309 | Original Document Information | |
| No summary! | ||
| 310 | Existing Content/DOM in Mozilla | |
| < MDC:Existing Content | ||
| 311 | External Redirects | MDC Project |
| The MDC wikis have the ability to redirect to external websites. We have done this so we can have links to external pages within the wiki that will be included in the wiki category pages. | ||
| 312 | Finding the right place to document bugs | |
| Bugzilla is big. Really really big. MDN is big too. This page helps to put two big things together. It: | ||
| 313 | Getting started as a new MDN contributor | Getting Started, MDC Project, MDN |
| The Mozilla Developer Network (MDN) is a wiki, where anyone can add and edit content. You don't need to be a programmer or an expert on the latest technology. There is a wide range of tasks that need to be done, ranging from the simple, such as proofreading and correcting typos, to the more complex, like writing API documentation. | ||
| 314 | MDN subproject list | Documentation, MDC Project, MDN |
| In order to turn the work of building documentation of All Things Open Web (not to mention All Things Mozilla) into something less daunting, sometimes it's helpful to split it up into subprojects. This page offers a list of links to MDN subproject organizational content. | ||
| 315 | MWC 2013 | Documentation, MDC Project, MDN, MWC |
| With Firefox OS scheduled to have a major presence at Mobile World Congress 2013, it's important that we have a fairly thorough suite of documentation for its various key components. This page will help us track what those components are, who's working on them, and what their statuses are. | ||
| 316 | Needs Redirect | |
| If you have | ||
| 317 | Team status board | Documentation, MDC Project, MDN |
| This table is a list of MDN contributors and what they're currently working on. Feel free to add yourself and what you're up to to this list, but keep in mind that we will purge out-of-date entries regularly, so if you choose to add yourself, do your best to keep your information current (even if all you do is update the "last updated" so we know you're keeping it current, despite your work taking a long time to finish). | ||
| 318 | Using the Mozilla Developer Center | Obsolete |
| Welcome to the Mozilla Developer Center! Here you'll find documentation for not only working on the code and other components of the Mozilla project, but also for developing add-ons for Mozilla-based software, creating new software based on Mozilla code, and web development for the open Web. | ||
| 319 | Welcome to the Mozilla Developer Network | MDC Project, MDN |
| The Mozilla Developer Network is the most comprehensive and accurate resource for Web development, as written by you, the developers. | ||
| 320 | MMgc | Tamarin |
| MMgc is the Tamarin (née Macromedia) garbage collector, a memory management library that has been built as part of the AVM2/Tamarin effort. It is a static library that is linked into the Flash Player but kept separate, and can be incorporated into other programs. | ||
| 321 | Newsgroup summaries | |
| No summary! | ||
| 322 | Format | |
| No summary! | ||
| 323 | Mozilla.dev.apps.firefox-2006-09-29 | |
| None this week. | ||
| 324 | Mozilla.dev.apps.firefox-2006-10-06 | |
| None this week. | ||
| 325 | mozilla-dev-accessibility | |
| No summary! | ||
| 326 | 2006-10-06 | |
| No summary! | ||
| 327 | 2006-11-10 | |
| No summary! | ||
| 328 | 2006-11-22 | |
| No summary! | ||
| 329 | mozilla-dev-apps-calendar | |
| No summary! | ||
| 330 | 2006-09-29 | |
| No summary! | ||
| 331 | 2006-10-06 | |
| No summary! | ||
| 332 | mozilla-dev-apps-firefox | |
| No summary! | ||
| 333 | 2006-09-29 | |
| None this week. | ||
| 334 | 2006-10-06 | |
| None this week. | ||
| 335 | 2006-10-13 | |
| No summary! | ||
| 336 | 2006-10-20 | |
| None this week. | ||
| 337 | 2006-10-26 | |
| None this week. | ||
| 338 | 2006-10-27 | |
| None this week. | ||
| 339 | 2006-11-03 | |
| None this week. | ||
| 340 | 2006-11-04 | |
| None this week. | ||
| 341 | 2006-11-10 | |
| None this week. | ||
| 342 | 2006-11-17 | |
| None this week. | ||
| 343 | 2006-11-24 | |
| None this week. | ||
| 344 | 2006-12-01 | |
| None this week. | ||
| 345 | mozilla-dev-apps-thunderbird | |
| No summary! | ||
| 346 | 2006-09-29 | |
| No summary! | ||
| 347 | 2006-10-06 | |
| No summary! | ||
| 348 | 2006-10-13 | |
| No summary! | ||
| 349 | 2006-10-20 | |
| No summary! | ||
| 350 | 2006-10-27 | |
| No summary! | ||
| 351 | 2006-11-03 | |
| No summary! | ||
| 352 | 2006-11-10 | |
| No summary! | ||
| 353 | 2006-11-17 | |
| No summary! | ||
| 354 | 2006-11-24 | |
| No summary! | ||
| 355 | 2006-12-01 | |
| No summary! | ||
| 356 | mozilla-dev-builds | |
| No summary! | ||
| 357 | 2006-09-29 | |
| 358 | 2006-10-06 | |
| No summary! | ||
| 359 | 2006-10-13 | |
| No summary! | ||
| 360 | 2006-10-20 | |
| No summary! | ||
| 361 | 2006-10-27 | |
| No summary! | ||
| 362 | 2006-11-03 | |
| No summary! | ||
| 363 | 2006-11-10 | |
| No summary! | ||
| 364 | 2006-11-17 | |
| No summary! | ||
| 365 | 2006-11-24 | |
| No summary! | ||
| 366 | 2006-12-01 | |
| No summary! | ||
| 367 | mozilla-dev-embedding | |
| No summary! | ||
| 368 | mozilla-dev-extensions | |
| No summary! | ||
| 369 | 2006-09-29 | |
| Return to mozilla-dev-extensions | ||
| 370 | 2006-10-06 | |
| Return to mozilla-dev-extensions | ||
| 371 | 2006-10-13 | |
| Return to mozilla-dev-extensions | ||
| 372 | 2006-10-20 | |
| Return to mozilla-dev-extensions | ||
| 373 | 2006-10-27 | |
| Return to mozilla-dev-extensions | ||
| 374 | 2006-11-03 | |
| Return to mozilla-dev-extensions | ||
| 375 | 2006-11-10 | |
| Return to mozilla-dev-extensions | ||
| 376 | 2006-11-17 | |
| Return to mozilla-dev-extensions | ||
| 377 | 2006-11-24 | |
| Return to mozilla-dev-extensions | ||
| 378 | 2006-12-01 | |
| Return to mozilla-dev-extensions | ||
| 379 | 2006-12-08 | |
| Return to mozilla-dev-extensions | ||
| 380 | Extentsions FAQ | |
| Return to mozilla-dev-extensions | ||
| 381 | mozilla-dev-i18n | |
| No summary! | ||
| 382 | 2006-09-22 | |
| No summary! | ||
| 383 | mozilla-dev-l10n | |
| No summary! | ||
| 384 | 2006-10-06 | |
| No summary! | ||
| 385 | 2006-10-13 | |
| No summary! | ||
| 386 | 2006-10-20 | |
| No summary! | ||
| 387 | 2006-10-27 | |
| No summary! | ||
| 388 | 2006-11-10 | |
| No summary! | ||
| 389 | 2006-11-17 | |
| No summary! | ||
| 390 | 2006-11-24 | |
| No summary! | ||
| 391 | 2006-11-3 | |
| No summary! | ||
| 392 | 2006-12-01 | |
| No summary! | ||
| 393 | 2006-12-08 | |
| No summary! | ||
| 394 | mozilla-dev-planning | |
| No summary! | ||
| 395 | 2006-07-17 | |
| No summary! | ||
| 396 | 2006-09-22 | |
| No summary! | ||
| 397 | 2006-10-06 | |
| Beltzner announced FF2 RC2 is availabe for all 3 major platforms in some 40 langauges. | ||
| 398 | 2006-10-13 | |
| No summary! | ||
| 399 | 2006-10-20 | |
| No summary! | ||
| 400 | 2006-10-27 | |
| No summary! | ||
| 401 | 2006-11-03 | |
| No summary! | ||
| 402 | 2006-11-10 | |
| No summary! | ||
| 403 | 2006-11-17 | |
| No summary! | ||
| 404 | 2006-11-24 | |
| No summary! | ||
| 405 | 2006-12-01 | |
| No summary! | ||
| 406 | mozilla-dev-platform | |
| Newsgroup summary for mozilla.dev.platform (Google Groups link) is for people working on the Mozilla Application Framework ("Mozilla-the-platform"). | ||
| 407 | 2006-09-29 | |
| Summary of newsgroup moz.dev.platform | ||
| 408 | 2006-10-06 | |
| No summary! | ||
| 409 | 2006-10-13 | |
| No summary! | ||
| 410 | 2006-10-20 | |
| No summary! | ||
| 411 | 2006-10-27 | |
| Summary: mozilla.dev.platform - October 21st to October 27th 2006 | ||
| 412 | 2006-11-03 | |
| Summary: mozilla.dev.platform - October 28th - November 3rd, 2006 | ||
| 413 | 2006-11-10 | |
| No summary! | ||
| 414 | 2006-11-17 | |
| Summary: mozilla.dev.platform - November 11th - November 17th, 2006 | ||
| 415 | 2006-12-01 | |
| Summary: mozilla.dev.platform - November 25th - December 1st, 2006 | ||
| 416 | 2006-18-24 | |
| Summary: mozilla.dev.platform - November 18th - November 24th, 2006 | ||
| 417 | mozilla-dev-quality | |
| No summary! | ||
| 418 | 2006-09-29 | |
| None | ||
| 419 | 2006-10-06 | |
| No summary! | ||
| 420 | 2006-10-13 | |
| No summary! | ||
| 421 | 2006-10-20 | |
| No summary! | ||
| 422 | 2006-10-27 | |
| None | ||
| 423 | 2006-11-03 | |
| None | ||
| 424 | 2006-11-10 | |
| None | ||
| 425 | 2006-11-17 | |
| None | ||
| 426 | 2006-11-24 | |
| None | ||
| 427 | 2006-12-01 | |
| No summary! | ||
| 428 | mozilla-dev-security | |
| No summary! | ||
| 429 | 2006-09-29 | |
| No summary! | ||
| 430 | 2006-10-06 | |
| No summary! | ||
| 431 | 2006-10-13 | |
| No summary! | ||
| 432 | 2006-10-20 | |
| No summary! | ||
| 433 | 2006-10-27 | |
| No summary! | ||
| 434 | 2006-11-03 | |
| No summary! | ||
| 435 | 2006-11-10 | |
| No summary! | ||
| 436 | 2006-11-17 | |
| No summary! | ||
| 437 | 2006-11-24 | |
| No summary! | ||
| 438 | 2006-12-01 | |
| No summary! | ||
| 439 | mozilla-dev-tech-js-engine | |
| No summary! | ||
| 440 | 2006-09-22 | |
| No summary! | ||
| 441 | 2006-09-29 | |
| No summary! | ||
| 442 | 2006-10-06 | |
| No summary! | ||
| 443 | 2006-10-13 | |
| No summary! | ||
| 444 | 2006-11-03 | |
| No summary! | ||
| 445 | 2006-11-10 | |
| No summary! | ||
| 446 | 2006-11-17 | |
| No summary! | ||
| 447 | 2006-11-24 | |
| No summary! | ||
| 448 | 2006-12-01 | |
| No summary! | ||
| 449 | JS-Engine FAQ | |
| No summary! | ||
| 450 | mozilla-dev-tech-layout | |
| No summary! | ||
| 451 | 2006-09-29 | |
| No summary! | ||
| 452 | 2006-10-27 | |
| None this week. | ||
| 453 | 2006-11-03 | |
| None this week. | ||
| 454 | 2006-11-10 | |
| None this week. | ||
| 455 | 2006-11-17 | |
| None this week. | ||
| 456 | 2006-11-24 | |
| None this week. | ||
| 457 | 2006-12- 02 | |
| None this week. | ||
| 458 | 2006-12- 08 | |
| None this week. | ||
| 459 | 2006-12-24 | |
| None this week. | ||
| 460 | mozilla-dev-tech-xpcom | |
| No summary! | ||
| 461 | 2006-09-06 | |
| No summary! | ||
| 462 | 2006-09-22 | |
| No summary! | ||
| 463 | 2006-09-30 | |
| No summary! | ||
| 464 | 2006-10-13 | |
| No summary! | ||
| 465 | 2006-10-27 | |
| No summary! | ||
| 466 | 2006-11-10 | |
| No summary! | ||
| 467 | 2006-11-17 | |
| No summary! | ||
| 468 | 2006-11-24 | |
| No summary! | ||
| 469 | 2006-11-3 | |
| No summary! | ||
| 470 | 2006-12-01 | |
| No summary! | ||
| 471 | 2006-12-08 | |
| No summary! | ||
| 472 | mozilla-dev-tech-xul | |
| XUL FAQ | ||
| 473 | 2006-09-22 | |
| No summary! | ||
| 474 | 2006-09-29 | |
| No summary! | ||
| 475 | 2006-10-06 | |
| No summary! | ||
| 476 | 2006-10-13 | |
| No summary! | ||
| 477 | 2006-10-20 | |
| No summary! | ||
| 478 | 2006-10-27 | |
| No summary! | ||
| 479 | 2006-11-03 | |
| No summary! | ||
| 480 | 2006-11-10 | |
| No summary! | ||
| 481 | 2006-11-17 | |
| No summary! | ||
| 482 | 2006-11-24 | |
| No summary! | ||
| 483 | 2006-12-01 | |
| No summary! | ||
| 484 | mozilla.dev.apps.calendar | |
| No summary! | ||
| 485 | 2006-10-13 | |
| None this week. | ||
| 486 | 2006-10-20 | |
| [Back to Weekly Summaries ] | ||
| 487 | 2006-10-27 | |
| [Back to Weekly Summaries ] | ||
| 488 | 2006-11-03 | |
| [Back to Weekly Summaries ] | ||
| 489 | 2006-11-10 | |
| [Back to Weekly Summaries ] | ||
| 490 | 2006-11-17 | |
| [Back to Weekly Summaries ] | ||
| 491 | 2006-11-24 | |
| [Back to Weekly Summaries ] | ||
| 492 | 2006-12-01 | |
| [Back to Weekly Summaries ] | ||
| 493 | mozilla.dev.tech.js-engine | |
| No summary! | ||
| 494 | 2006-10-06 | |
| No summary! | ||
| 495 | Security | |
| Relying on these obsolete security articles is highly discouraged. Doing so may put your systems at risk. | ||
| 496 | Digital Signatures | Security, Tutorial |
| Encryption and decryption address the problem of eavesdropping, one of the three Internet security issues mentioned at the beginning of this document. But encryption and decryption, by themselves, do not address another problem: tampering. | ||
| 497 | Encryption and Decryption | Security, Tutorial |
| Encryption is the process of transforming information so it is unintelligible to anyone but the intended recipient. Decryption is the process of transforming encrypted information so that it is intelligible again. | ||
| 498 | Introduction to Public-Key Cryptography | Security, Tutorial |
| Public-key cryptography and related standards and techniques underlie the security features of many products such as signed and encrypted email, single sign-on, and Secure Sockets Layer (SSL) communications. This document introduces the basic concepts of public-key cryptography. For an overview of SSL, see "Introduction to SSL." For an overview of encryption and decryption, see "Encryption and Decryption." Information on digital signatures is available from "Digital Signatures." | ||
| 499 | Introduction to SSL | Security |
| This document introduces the Secure Sockets Layer (SSL) protocol. SSL has been universally accepted on the World Wide Web for authenticated and encrypted communication between clients and servers. | ||
| 500 | NSPR Release Engineering Guide | NSPR, Outdated_articles |
| This paper is for engineers performing formal release for the NetScape Portable Runtime (NSPR) across all platforms. | ||
| 501 | Solaris 10 Build Prerequisites | |
| No summary! | ||
| 502 | Using SSH to connect to CVS | Developing Mozilla |
| No summary! | ||

